This message was deleted.

sparse-intern-71089

02/06/2024, 4:24 PM

This message was deleted.

limited-art-90541

02/06/2024, 5:03 PM

I have figured out that it is just not picking up my tsconfig path and that I can set it via the environment variable:

PULUMI_NODEJS_TSCONFIG_PATH

Is there a way to set this in my project configuration or I need to export this in my shell everytime I work with pulumi?

icy-controller-6092

02/06/2024, 5:55 PM

runtime: name: nodejs options: typescript: false nodeargs: --import tsx/esm

icy-controller-6092

02/06/2024, 5:56 PM

This will replace Pulumi typescript compiler (TS-node) with the much better & faster tsx compiler

icy-controller-6092

02/06/2024, 5:57 PM

It will find your tsconfig.json automatically

icy-controller-6092

02/06/2024, 5:58 PM

I’ve also done a lot of work getting multiple Pulumi projects setup in an nx monorepo, happy to look into any code you might have

limited-art-90541

02/06/2024, 6:11 PM

Hi Matt. This is very interesting, but a little new to me so I am not sure I understand the solution. I am using a locally installed dev dependency to check my typescript files and run

tsc -w --noEmit

at the root folder. I don't mind trying tsx/esm but will it find my tsc version? Or will it use a different compiler? Any context would be appreciated

limited-art-90541

02/06/2024, 6:13 PM

Ok I am seeing it uses esbuild under the hood to strip the typescript, and so its on me to do the typechecking locally correct?

Open in Slack

Previous Next

Pulumi Community

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.