-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
chore: migrate to ESLint flat config #26583
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
Conversation
|
@antfu Do you have any guidance for getting the |
For |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I think this could be a good starting point. I will refactor them out and move some rules into @nuxt/eslint-config
in future PRs.
Thanks for sorting @antfu ๐ Much appreciated. |
Co-authored-by: Damian Gลowala <[email protected]>
๐ Linked issue
Resolves #25351
๐ Description
As discussed in #25351, eslint are upgrading their config system in eslint v9. The new syntax is available now but is opt-in. We can opt in by replacing
.eslintrc
with aeslint.config.js
file or setting the environment variableESLINT_USE_FLAT_CONFIG=true
before running eslint.I have followed eslint's configuration migration guide to replace the configuration. This PR is intended to be a straight swap, not modifying the configuration in any way, just upgrading the syntax. There may be additional work needed to take advantage of the benefits the new syntax brings.
๐งช How to test
ESLINT_USE_FLAT_CONFIG=true pnpm run lint
โฌ๏ธ Dependencies
Nuxt depends on several configs and plugins. Below is the status of flat config support for each dependency. (Data sourced from tracker)
Current issues: