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

Docs: eslint v9 #7909

Open
ramirezj opened this issue Apr 6, 2024 · 2 comments · May be fixed by #8054
Open

Docs: eslint v9 #7909

ramirezj opened this issue Apr 6, 2024 · 2 comments · May be fixed by #8054
Labels
area: docs Improvements or additions to documentation good first issue Good for newcomers owned-by: turborepo

Comments

@ramirezj
Copy link

ramirezj commented Apr 6, 2024

What is the improvement or update you wish to see?

Documentation on supporting users who have migrated to the new eslint.config.js config file or who want to continue to use estlintrc but run >= v9 of eslint

Aiming to take a look at this myself, but flagging in case someone has more time to spend on this or a solution already

Is there any context that might help us understand?

With the recent v9 release of eslint, it now uses flat config files by default and support for the deprecated eslintrc config file will be removed entirely in v10

Does the docs page already exist? Please link to it.

https://turbo.build/repo/docs/handbook/linting/eslint

@arlyon arlyon added the area: docs Improvements or additions to documentation label Apr 8, 2024
@anthonyshew
Copy link
Contributor

Would definitely appreciate help on this one! I just explored this a little bit and it looks like this will be a net-positive change for Turborepo users, but haven't had time to explore figuring out the new syntax.

@ramirezj
Copy link
Author

Digging in between other work, FYI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Improvements or additions to documentation good first issue Good for newcomers owned-by: turborepo
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants