Targets before ES2022 still use Object.hasOwn?

[sparr]

Maybe I'm just not understanding something, but I've reduced this to a test case and want to figure out what's going on.

//test.js
Object.hasOwn(Object, "hasOwn");

swc test.js -C jsc.target=ES2015
outputs the same code, despite Object.hasOwn not being valid in ES2015. I tested with every valid target and got the same result. I also tested with -C env.targets.chrome=21, and with those configs in .swcrc instead of on the command line, with no change in results.

[kdy1]

You need corejs polyfill, and if you want to transpile the code, there’s no tool I know of that supports such tranpilation

[kdy1]

SWC supports injecting corejs polyfill automatically, though

[sparr]

With this config:

{
    "env": {
        "targets": {
            "node": "10"
        },
        "mode": "usage",
        "coreJs": "3.47.0"
    }
}

I can produce this output:

import "core-js/modules/es.object.has-own.js";
Object.hasOwn(Object, "hasOwn");

which is progress... but I came into this with a single js file produced by a bundling application, and I need to leave with a single file. Am I going to need to do another separate bundling stage after this?