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

Yarn workspaces handle this fine. Yarn classic and Yarn 2+ both work. You can't use PnP, but putting `nodeLinker: node-modules` in your .yarnrc.yml solves that.

You don't need to use `yarn link`. The hoisted node_modules is used for everything. If you run into problems with hoisting (e.g. you're building AWS lambdas or other "nested" code that runs in a different runtime), you can turn off hoisting and add an explicit dependency to the other workspaces using this package.json notation:
```        "@otherWorspacePackageName": "workspace:^",```

Happy to help with any questions on this (I've just been through it again over the last few days, converting a large old project to use it). It doesn't look like our time zones overlap too much though, so the cycle time might be very high :disappointed:

Awesome thanks I'll try this out after work. You say you've just been through this over the last few days, would that project code happen to be public on the internet somewhere?

No, sorry. But there is really only the one thing needed for Pulumi in a Yarn project: the nodeLinker line in your yarnrc.yml. Everything else is straight from the Yarn docs.

I finally had a chance to try this out and was not successful. I have a packages/fabric with a project component and an examples/project which uses it and running `pulumi preview` results in typescript not finding packages/fabric. I'm not sure if it's a yarn issue or typescript.