Update nodejs SDK to use optional chaining in constructor

[lblackstone]

Proposed changes

Related issues (optional)

[lukehoban]

Are we okay taking a dependency on TypeScript 3.7 features? I'm not positive we have any strict dependency on 3.7 yet. We recently bumped the typescript version we bring along in @pulumi/pulumi, and may have bumped to a version that supports this - inn which case we should ensure that @pulumi/kubernetes requires a new enough version to ensure it gets this version of TypeScript.

Also - I assume these get erased back down to && by the TypeScript compiler? I believe Node itself does not yet support ?. natively.

[lblackstone]

Are we okay taking a dependency on TypeScript 3.7 features? I'm not positive we have any strict dependency on 3.7 yet. We recently bumped the typescript version we bring along in @pulumi/pulumi, and may have bumped to a version that supports this - inn which case we should ensure that @pulumi/kubernetes requires a new enough version to ensure it gets this version of TypeScript.

It got pulled in from @pulumi/pulumi, so I assumed it was safe to rely on 3.7 features. LMK if that's not the case.

Also - I assume these get erased back down to && by the TypeScript compiler? I believe Node itself does not yet support ?. natively.

Here's what the resulting JS looks like:

        props["data"] = (_a = args) === null || _a === void 0 ? void 0 : _a.data;

from this TS:

          props["data"] = args?.data;

[lukehoban]

Here's what the resulting JS looks like:

Kind of humorous that we are making one layer of code generation "nicer", which leads the next layer of code generation to be net less nice :-).