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

Has anyone got a functional launch.json or similar, to get debugging working with Pulumi?

Even _partially_ working would be fine. If it could run my tests, it'd be great. I've never managed to get js debugging working, ever... must be because I run ts/node via Docker...

<@UE1LN7A22> How do you guys test pulumi apps?

<@U012UJTT55M> Yeah, this worked for me: <https://github.com/pulumi/pulumi/issues/1372#issuecomment-794491331>

It should probably be in the docs. I actually switched away from the suggested method of running a task as VScode complains about not having a problem matcher and their docs seemed daunting on that aspect. I also found it would occasionally get stuck and the output is missing.

Instead I just `NODE_OPTIONS='--inspect-brk=127.0.0.1:9292' pulumi up --parallel=1`  from the terminal and then `F5` in vscode to launch the debugger.

I haven't managed to figure any of that out. My use case is different.. I'm running mocha, not Pulumi, so it should be even easier.. but I'm just not getting it.
Guess I've been stuck in the JVM too long.. new ways of working...

Found an "auto-attach" feature that suddenly makes stuff work... <https://code.visualstudio.com/docs/nodejs/nodejs-debugging>

The _--inspect-brk=127.0.0.1:9292_ option that all the Pulumi docs mention just caused everything to hang. With that option gone, stuff ran but the debugger never attached. With this auto-attach (set to "smart"), I can now debug my tests.