fix(es/preset-env): Disable all class passes for target with native class support

[kdy1]

Description:

This is just PoC to ask for opinion @magic-akari. I think it sounds reasonable to disable all class properties transform where it's natively supported. So I made this, but I want to hear opinion about it.

Related issue:

• Closes Disable define/set issue transform for targets with native class properties support #9743

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9e654fa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codspeed-hq]

CodSpeed Performance Report

Merging #9774 will not alter performance

_{Comparing kdy1:issue-9743 (9e654fa) with main (bd77f44)}

Summary

✅ 194 untouched benchmarks

[magic-akari]

I tested it in Babel's Playground. With native support for class fields, there are indeed no related transformations.
However, this raises concerns about TypeScript's useDefineForClassFields option.

[kdy1]

Does it work even for the targets with native class support?

[magic-akari]

Does it work even for the targets with native class support?

Yes, in TypeScript, even with native support for class fields, useDefineForClassFields can still influence the generated code.

input:

class Foo {
    bar: any;
}

output:
https://www.typescriptlang.org/play/?useDefineForClassFields=true&target=99#code/PTAEAEFcGcFMBFYDMCWA7WAxA9gJwMIA2AhtNJirIQCbQBcoALrpLAFAgSPG4DmsjBrGgYAHozZsAxiTKgc2UAG82oNaABGPBsTQBPANxsAvkA

"use strict";
// @useDefineForClassFields: true
// @target: esnext
class Foo {
    bar;
}

output:
https://www.typescriptlang.org/play/?target=99&useDefineForClassFields=false#code/PTAEAEFcGcFMBFYDMCWA7WAxA9gJwMIA2AhtNJirIQCbQBcoSxhcAUCBAC7G4DmsnBrGgYAHp1asAxiTKgc2UAG9WoNaABGPBsTQBPANysAvkA

"use strict";
// @useDefineForClassFields: false
// @target: esnext
class Foo {
}

[magic-akari]

Perhaps we should redesign the transformation options for the class fields; I suggest we include at least three options:

• spec [[DEFINE]]
• [[SET]]
• loose (preserve class fields if native support is available, otherwise use [[SET]] semantics)

[Austaras]

Perhaps we should redesign the transformation options for the class fields; I suggest we include at least three options:

* spec `[[DEFINE]]`

* `[[SET]]`

* loose (preserve class fields if native support is available, otherwise use `[[SET]]` semantics)

Maybe 1 and 3 would be enough?