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

ESLint flat config support #73

Open
mrmckeb opened this issue Oct 20, 2023 · 2 comments · May be fixed by #114
Open

ESLint flat config support #73

mrmckeb opened this issue Oct 20, 2023 · 2 comments · May be fixed by #114
Labels
enhancement New feature or request eslint
Milestone

Comments

@mrmckeb
Copy link
Contributor

mrmckeb commented Oct 20, 2023

We plan to implement support for ESLint's new flat config format around the time that ESLint v9.0.0 launches. At that time, this will be the default config format for ESLint.

Until that time, anyone moving to v9.0.0 (or a pre-release) can set the ESLINT_USE_FLAT_CONFIG environment variable to false as a workaround.

The move to the flat config will be a breaking change in this package.

See this post for more:
https://eslint.org/blog/2023/10/flat-config-rollout-plans/

@mrmckeb mrmckeb added enhancement New feature or request eslint labels Oct 20, 2023
@mrmckeb mrmckeb pinned this issue Oct 20, 2023
@mrmckeb mrmckeb changed the title Flat config support ESLint flat config support Oct 20, 2023
@mrmckeb mrmckeb added this to the v7 milestone Mar 4, 2024
@mwskwong
Copy link
Contributor

mwskwong commented Apr 6, 2024

Just wanna add that ESLint v9 has hit stable, with flat config being the default. It may be worth focusing on moving to flat config now

@musjj
Copy link

musjj commented Oct 24, 2024

Now that Next.js v15 with ESLint v9 support is out, will we get flat config support soon?

@appano1 appano1 linked a pull request Nov 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request eslint
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants