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

This happened to one of our devs yesterday, but not to any of the rest of us. It was caused by a workaround we use for building lambdas.
We have a symlink from the monorepo's package.json to each project that builds lambdas, and during the build, a separate node_modules is created in each of those folders. The dev had to remove all the node_modules folders and rebuild.

This is the first time this happened in many months. Normally you don't need to worry about it.

it's 100% reproducible after a clean yarn install in CICD, so I'm wondering what am I doing wrong

FWIW, `rm yarn.lock &amp;&amp; yarn install` fixes it

so I guess it was some transitive dependency of something ¯\_(ツ)_/¯ . Javascript is a mess :slightly_smiling_face: