Skip to content
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

[Feature Request] Implement flat config compatibility #173

Closed
thakyZ opened this issue Apr 9, 2023 · 1 comment · Fixed by #175
Closed

[Feature Request] Implement flat config compatibility #173

thakyZ opened this issue Apr 9, 2023 · 1 comment · Fixed by #175

Comments

@thakyZ
Copy link

thakyZ commented Apr 9, 2023

I would love to see the ability to implement flat configuration as a suppliable eslint config.

prantlf added a commit to prantlf/grunt-eslint that referenced this issue Apr 10, 2024
Upgrade the eslint dependency. Change the documentation and tests to use
the new configuration format. Also, upgrade Node.js in the build pipeline.

> When ESLint v10.0.0 is released (end of 2024 or early 2025 in all likelihood),
  the eslintrc configuration system will be completely removed.

https://eslint.org/blog/2023/10/flat-config-rollout-plans/#eslintrc-removed-in-eslint-v10.0.0

* Describe and test the usage only with flatconfig. It'll be the only config
  format soon. Who needs to retain `.eslintrc` can stay with eslint 8.
* ESLint 9 supports only Node.js `^18.18.0 || ^20.9.0 || >=21.1.0`.
* The formatter `eslint-tap` works, but because it doesn't follow the NPM
  package naming convention `eslint-formatter-*`, it has to be specified
  using a path to the script with the main exports.
@prantlf
Copy link
Contributor

prantlf commented Apr 11, 2024

The support has landed in 25.0.0. Thanks a lot, Sindre!

The flatconfig enabled by default wasn't the only change in ESLint 9. There're also changes in the API. Even if you fix the configuration, you still may not be able to upgrade, if some of your ESLint plugins aren't compatible with ESLint 9 yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants