💻
What problem are you trying to solve?
In #13752 we have materialized the estree plugin option classFeatures. This makes it impossible to support ESLint 7 when using @babel/parser 8 with @babel/eslint-parser, because ESLint plugins developed for ESLint 7 has to adopt the Babel AST for the features like class properties and private methods.
Describe the solution you'd like
Since it is major version, we can bump the ESLint requirements. I suggest we bump it to 8.9.0, published a year ago, which is the first version shipped with the es2022 environment support. We can even bump to a higher version if there are preferred features.
Describe alternatives you've considered
Revert #13752 and keep supporting ESLint 7.
Documentation, Adoption, Migration Strategy
The @babel/eslint-parser 7 already supports ESLint 8. So this change will not affect ESLint 8 users. For ESLint 7 users, they have to upgrade to ESLint 8 before upgrading to @babel/eslint-parser 8.
💻
What problem are you trying to solve?
In #13752 we have materialized the
estreeplugin optionclassFeatures. This makes it impossible to support ESLint 7 when using@babel/parser8 with@babel/eslint-parser, because ESLint plugins developed for ESLint 7 has to adopt the Babel AST for the features like class properties and private methods.Describe the solution you'd like
Since it is major version, we can bump the ESLint requirements. I suggest we bump it to
8.9.0, published a year ago, which is the first version shipped with thees2022environment support. We can even bump to a higher version if there are preferred features.Describe alternatives you've considered
Revert #13752 and keep supporting ESLint 7.
Documentation, Adoption, Migration Strategy
The
@babel/eslint-parser7 already supports ESLint 8. So this change will not affect ESLint 8 users. For ESLint 7 users, they have to upgrade to ESLint 8 before upgrading to@babel/eslint-parser8.