You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe:
Following the new version of ESLint 9 (published on 05/04/2024), the eslint-config package is no longer compatible due to a change in the ESLint 9 configuration.
Please describe your solution:
The eslint-config package must be updated to ensure compatibility with ESLint 9. However, before this work can be undertaken, all plugins and configurations used must also be compatible with ESLint 9.
Describe the alternatives you have considered:
An alternative might be to find replacements for any plugins or configurations that are not compatible with ESLint 9.
Additional context:
There are no plans to maintain compatibility with ESLint 8, so there will be a breaking change.
Status of plugins and configurations compatibility with ESLint 9 :
For eslint-plugin-vitest-globals, it is no longer necessary to wait for an update to support the new eslint configuration, as it is now integrated into eslint-plugin-vitest, see the PR #435
Is your feature request related to a problem? Please describe:
Following the new version of ESLint 9 (published on 05/04/2024), the eslint-config package is no longer compatible due to a change in the ESLint 9 configuration.
Please describe your solution:
The eslint-config package must be updated to ensure compatibility with ESLint 9. However, before this work can be undertaken, all plugins and configurations used must also be compatible with ESLint 9.
Describe the alternatives you have considered:
An alternative might be to find replacements for any plugins or configurations that are not compatible with ESLint 9.
Additional context:
There are no plans to maintain compatibility with ESLint 8, so there will be a breaking change.
Status of plugins and configurations compatibility with ESLint 9 :
The text was updated successfully, but these errors were encountered: