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

Check out the notes at the bottom of this page: <https://www.pulumi.com/docs/intro/languages/javascript/>

Essentially, you can configure anything you like for module and target; your IDE will use those.

Pulumi will use target es6 and module commonjs, unless you turn off Typescript support.

You should lose no functionality if you turn off the built-in Typescript support, you just have to manage all the options yourself.

The app was generated with `es2016`  and not `es6`

If you're confident in your tsconfig / register=ts-node magic, then manage it yourself, you'll get your own preferred environment.

Ah, maybe they've update that to es2016 but forgot to update the docs.

There is no best practice, I think. It's a bit like deciding between using the aws and awsx packages when buliding your VPC. Both are good, you just pick which is right for you.

I guess I would need to compile it on my own and pipe the results to pulumi

generally you'd run your typescript program with the pulumi CLI, unless you're using the Pulumi CLI

I’m slightly confused.

If I want the lambdas to contain the most minimal possible code, I would like it to use native JS code instead of transpiling it

how can I use custom `tsconfig` options while piping the output to pulumi cli?

would be good to get a little context on what your desired goal is

<@UCWG26BH7> Right now it seems like the built-in typescript support is for `commonjs` modules and `es2016` which is good but it transpiles the code into a less readable code. I would like to know if it’s possible to transpile the code into a “modern” JS syntax