SWC transpiles optional chaining even tho it shouldn't

[danieltroger]

Describe the bug

Possible regression of #1704 ?
SWC transpiles optional chaining for node, even when setting target to latest node which supports optional chaining.

Input code

globalThis?.hello?.world?.("sup?");

Current output code:

var ref, ref1;
globalThis === null || globalThis === void 0 ? void 0 : (ref = globalThis.hello) === null || ref === void 0 ? void 0 : (ref1 = ref.world) === null || ref1 === void 0 ? void 0 : ref1.call(ref, "sup?");

Config

{
  "env": {
    "shippedProposals": true
  }
}

"browserslist": "node >=16.4.2",

Expected behavior

globalThis?.hello?.world?.("sup?");

Version
The version of @swc/core:

@swc/cli: 0.1.46
@swc/core: 1.2.64

Additional context
Idk but it feels like not transpiling it might be faster at runtime

Repro .zip:
swc-optional-chaining.zip

[kdy1]

It's caused by https://github.com/babel/babel/blob/main/packages/babel-compat-data/data/plugins.json not containing proper node version of proposal-optional-chaining.
I'm not sure where should I get the compat data.

[Austaras]

It does now

[kdy1]

Closing as fixed by #3072

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.