feat!: drop legacy configs, requires ESLint v9 and ESM #534
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is intended to be released as v1.0.
In this PR:
.eslintrc
format supportThis PR is more like a clean-up.
For users that use
@nuxt/eslint
module with theeslint.config.mjs
config, everything should keep working as-is with no migration needed.This change will break the usage for users that are using our new config with legacy eslintrc format, for example:
...which I expect should be a rare case, and in the worst case, they can still use the existing
0.7.x
.