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

All of this is handled manually or via packaging tools or libraries. If you're using plain tsc, you can get most of the way by specifying outDir in your tsconfig.json. After compiling, copy your package.json in there and package up that directory.

Thanks, I found out myself.
Now I am researching into differences between `CommonJS` and `NodeNext`  ESM imports

<https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#esm-nodejs>

It looks like you mess with the paths for imports

<https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#esm-nodejs>

I will try to play around and see if I can get it working with pulumi. According to issues on github it should be supported since ~3.22.0

Yes it's all working. The only thing that isn't working is Yarn2's PnP: you have to use `nodeLinker: node-modules` in your Yarn config, if you use Yarn2.

Note that for ESM, you need to add this to every Pulumi.yaml:
```runtime:
  name: nodejs
  options:
    nodeargs: "--loader ts-node/esm --no-warnings"```

It's documented in the GitHub PR that adds this feature.. not sure if it's documented elsewhere...