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

I'm using the same tsconfig.json for both tests and Pulumi.

My tests package.json has:
```    "target": "es2020",
    "type": "module",```

The module that's importing the non-ESM package has this in its package.json:
```    "type": "module",
    "module": "esnext",
    "target": "es2020",```

And my Pulumi project's package.json has this:
```    "target": "es2020",```

And all three packages are workspaces in a Yarn4 project. The root package.json has this:
```  "module": "esnext",
  "target": "es2020",```

I've been playing with hoisting, getting different error messages. It is possible to eliminate this error by having the relevant dependencies in the correct workspace's node_modules folder, instead of (or as well as) having it hoisted to the root.

Unfortunately I don't really understand the new installConfig.hoistingLimits setting, and I don't know how to get a full node_modules into one workspace, while leaving all the others using hoisted dependencies as much as possible.