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

<@U02JSMS8EHM> good luck. I tried it once, but failed. The assumption that there *is* a `node_modules` folder is deep in the implementation of Pulumi core.
<https://github.com/pulumi/pulumi/pull/4349>

Oh, you did seriously try it!

I'd be happy finding a way for the pulumi program to be able to find the @pulumi/* packages (i am already refactoring inlined lambdas as separate packages).

&gt; finding the Pulumi plugins is iterating over the `node_modules` folder in Go code to find the plugin binaries.
This is definitely blocking :(

<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/|The docs> says pulumi can be installed with yarn. This leads people to believe that it works with yarn. And people usually switch from npm to yarn to benefit from hoisting. But as soon as they try to hoist packages (or PnP), it doesn't work. Pulumi only works with the node-modules linker and when disabling hoisting (for the whole monorepo or at least for the package that contains the pulumi program).
I'd be happy to provide a PR to help others, but I am not sure when this belongs.

we use yarn 3 as well, but use the node_modules fallback option over pnp. That works, never gotten pnp to work