Hi, Guys! I am truly glad to hear that Pulumi 2.0 has been released! I believe in the superpower of Pulumi. btw, Why does Pulumi use ES2016 as a default target of compiler option? This attachment is a pic of initial tsconfig after installation of Pulumi and execution of

pulumi new

.

The tsconfig settings in our templates are generally what we’d recommend. We’re thinking about bumping the target in our templates to

es2018

as it has broad support in Node 10+.

Thank you for quick response! I get it. I set es2016 as the target.

I tried running my stacks with following tsconfig (borrowed from other project) and didn't detect any regression:

"compilerOptions": {
        "strict": true,
        "outDir": "bin",
        "target": "ESNext",
        "module": "commonjs",
        "moduleResolution": "node",
        "sourceMap": true,
        "experimentalDecorators": true,
        "pretty": true,
        "noFallthroughCasesInSwitch": true,
        "noImplicitReturns": true,
        "forceConsistentCasingInFileNames": true,
        "strictNullChecks": true,
        "strictFunctionTypes": true,
        "strictPropertyInitialization": true,
        "strictBindCallApply": true,
        "noImplicitThis": true
    }

@acceptable-stone-35112 Oh!!!! Thank you for sharing your tsconfig! I am gonna dissect it on my env 😄