Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'no-class-fields' work not good for firefox@75 #134

Closed
xiaoxianjie opened this issue Apr 7, 2024 · 3 comments
Closed

'no-class-fields' work not good for firefox@75 #134

xiaoxianjie opened this issue Apr 7, 2024 · 3 comments

Comments

@xiaoxianjie
Copy link

Instance public fields supported from firefox@69
Static public fields supported from firefox@45

my browserslist: ['firefox >= 75']

but, the code below

class {
  a = 1;
  static b = 2;
}

it will throw some errors as ES2022 field 'a' is forbidden., ES2022 static field 'b' is forbidden.

i need only to disable the private_class_fields and private_class_methods;

@ota-meshi
Copy link
Member

This plugin does not refer to browserlist, config your preferences yourself.

@ota-meshi ota-meshi closed this as not planned Won't fix, can't repro, duplicate, stale Apr 7, 2024
@xiaoxianjie
Copy link
Author

Maybe my words made you misunderstand.
i mean's,
this rule can be spilt?
then, i can enable public property and disable the private property.

@ota-meshi
Copy link
Member

Ah, I see. I think rule splitting is possible, but I think it needs to be done in major versions.
What "syntax" units do you think would be useful to split rules into in order to control compatibility with Firefox, other browsers, and Node.js?
Could you please open a new issue and suggest?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants