This message was deleted.

What exactly is it you are trying to compile? And with what version of

tsc

? And with what tsconfig.json?

@white-balloon-205 Sorry for bothering. Thanks for your questions which helped 🙂 It was the too old Typescript version installed globally (

3.3.4000

) 🙈 I think

$(npm bin)/tsc

would be the better way to avoid this.

Got it - makes sense. Note that Pulumi itself doesn't run

tsc

for you - by default Pulumi uses a built-in version of TypeScript that it depends on via

tsnode

which should never hit the problem above. Sounds like you are opting to compile yourself - which likely is something you are doing with a build step you are managing yourself?

Yes. We use

tsc

as a step for publishing our NPM package which has a Pulumi class in it. Is there a way doing this with

pulumi

CLI?

I see. Yes - for reusable components and packages, definitely does make sense to run

tsc

manually, and you are right that in that case you will want to make sure to use the same version of

tsc

. My comments above were about deploying apps directly.

Ah, good to know that we’re on the right track, then 🙂 Are the sources for the blog posts also on Github? Or should I simply create an issue for it instead?

Yep - sources are here - PR welcome! https://github.com/pulumi/docs/blob/master/content/blog/creating-and-reusing-cloud-components-using-package-managers/index.md