No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@U012UJTT55M> Yes. That’s we’re doing. We’re collecting internal thrown errors and then want to stop Pulumi proceeding with throwing them all at once.

Perhaps I’ve asked the wrong question. Let’ see:

What’s the intended way to stop Pulumi’s preview or update within Typescript code? Something else than throwing an error?

Throwing an error is the best way to stop a Pulumi application. This allows the Pulumi engine to do some of its own "cleanup" work at the end of execution.

<@UDEJ1F5SQ> Thanks. So, then back to my initial question: How can you suppress the stacktrace Pulumi shows?
(I remember seeing a solution here in Slack, but it seems hidden in the 10k-messages limit).

I'm not aware of a way to suppress the stack trace from being printed.