Or rather how can I use `target es2020 ` and compile the pro

Question

Or rather how can I use `target es2020 ` and compile the project myself piping the output JS to Pulumi

billowy-army-68599 · Answer

pulumi uses ts node to automatically run `tsc` if you want to compile the JS yourself you can set the following in your `Pulumi yaml` ```options typescript false```

lemon-monkey-228 · Answer

How do we then leverage this to deploy

lemon-monkey-228 · Answer

Manually compile and `pulumi up`

lemon-monkey-228 · Answer

```name creatio sync description Creatio Sync runtime nodejs options typescript false``` is my `Pulumi yaml`

lemon-monkey-228 · Answer

If I run `npx tsc index ts` it compiles the `index js`

lemon-monkey-228 · Answer

But `pulumi up` still seems to be trying to use it

lemon-monkey-228 · Answer

Do I need a change in my `package json` or something too

lemon-monkey-228 · Answer

Either the options changed recently or I m stupid but it s now ```runtime name nodejs options typescript false``` but still no dice

billowy-army-68599 · Answer

when you say `pulumi up` seems to be trying to use it do you mean your index ts

elegant-pager-5412 · Answer

I managed to get it working but it is not that straight forward my `tsconfig json` specifies that the output dir should be `dist` which is ignored in ` gitignore` Then I needed to tell Pulumi to use the JS file which we can do so by adding the `main` property to the `package json` The thing is that unless we use `amd` as the `module` definition in `tsconfig` TSC cannot combine all files into a single `index js` file To solve this I did some bash magic and created the following command ``` scripts deploy tsc amp amp sed i s main main $ find dist name index js print maxdepth 3 quit package json amp amp pulumi up ```

lemon-monkey-228 · Answer

sorry yeah and I m assuming it is

elegant-pager-5412 · Answer

This works for me I guess the script should be slightly modified for others

elegant-pager-5412 · Answer

my `tsconfig json` ``` compilerOptions strict true outDir dist target es2020 module commonjs moduleResolution node sourceMap true experimentalDecorators true emitDecoratorMetadata true esModuleInterop true resolveJsonModule true pretty true noFallthroughCasesInSwitch true noImplicitReturns true strictNullChecks true noImplicitAny true noImplicitThis true alwaysStrict true strictPropertyInitialization false forceConsistentCasingInFileNames true removeComments true ```

lemon-monkey-228 · Answer

My exact issue is ```Diagnostics pulumi pulumi Stack creatio sync production error Running program Users james projects creatio creatio sync deploy failed with an unhandled exception Users james projects creatio creatio sync deploy node modules devops pulumi utils index ts 1 import as fs from fs ^^^^^^ SyntaxError Cannot use import statement outside a module```

lemon-monkey-228 · Answer

I d have thought it d blown up at `npx tsc` if the settings were till wrong feel free to correct me if I m wrong

elegant-pager-5412 · Answer

Try setting the module to commonjs

lemon-monkey-228 · Answer

``` compilerOptions strict true outDir bin target es2020 module commonjs moduleResolution node sourceMap true experimentalDecorators true esModuleInterop true resolveJsonModule true pretty true noFallthroughCasesInSwitch true noImplicitReturns true forceConsistentCasingInFileNames true ```

lemon-monkey-228 · Answer

``` name creatio sync main bin index js devDependencies types node ^10 0 0 dependencies devops pulumi utils ^0 1 2 pulumi kubernetes ^2 0 0 pulumi kubernetesx ^0 1 1 pulumi pulumi ^2 0 0 ```

lemon-monkey-228 · Answer

It s a dependency that s causing the issue

lemon-monkey-228 · Answer

feels like I need to cascade the `tsc` call to the library too

lemon-monkey-228 · Answer

Fixed the issue Turns out my inexperience with TS meant I was packaging a helper as TS and not the transpiled JS