-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(linter): allow ESLint Flat Config to be opted into manually #16858
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
if ( | ||
useFlatConfig && | ||
eslintConfigPath && | ||
!eslintConfigPath?.endsWith('eslint.config.js') |
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.
Nit: The optional chaining
on line 27 is not needed, since we check for eslintConfigPath
's existence on line before
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
ESLint's new (not yet default) so called "Flat Config" cannot be used with Nx workspaces.
Expected Behavior
Users can manually opt into using ESLint's Flat Config style in their Nx workspaces prior to it being the official primary configuration style in ESLint v9 later in the year.
Appropriate migrations and generators will follow on from this once we get much closer to Flat Config being the primary default in ESLint.
https://eslint.org/docs/latest/use/configure/configuration-files-new
P.S. I also took the opportunity to clean up how ESLint is resolved and instantiated, it had become organically a bit messy over time