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

Alright, I’ve found it.
Digging into the source code and some of the issues on github learned me I have to set the environment variable `PULUMI_TEST_MODE=true` .

Yes, or you can run your test code inside `pulumi.runtime.runInPulumiStack()`.

Often it is possible to avoid doing either, if you limit your testing to your ComponentResources and avoid testing your _index.ts_ or similar.

So far, the only time I have had to use `runInPulumiStack` in a test was to test `registerStackTransformation`.

I wasn’t aware of `pulumi.runtime.runInPulumiStack()` I’ll take a look at that.

Up until now I never tested index.ts. index.ts only does the wiring. I only test the resources created by my classes or functions that kind of do what `ComponentResources` does. I also wasn’t aware of that one :face_with_rolling_eyes: :smile:

And it is exactly while testing these functions and classes (that rely on a Node.js package that uses Pulumi) that I got that error message

Ok. I use a mono-repo so not quite the same case. I haven't been dependent on that env var. But it looks like it's intended for exactly this purpose :+1:

Well, at least it solved my problem. But for some reason, nodejs memory usage exploded. I had to increase `--max-old-space-size`