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

migrate to typescript-eslint v6 #298

Closed
Tracked by #303
danielroe opened this issue Jul 11, 2023 · 3 comments · Fixed by #332
Closed
Tracked by #303

migrate to typescript-eslint v6 #298

danielroe opened this issue Jul 11, 2023 · 3 comments · Fixed by #332

Comments

@danielroe
Copy link
Member

https://typescript-eslint.io/blog/announcing-typescript-eslint-v6/

@danielroe danielroe mentioned this issue Aug 9, 2023
@shinGangan
Copy link
Contributor

Hey @danielroe .
If you don't have someone in charge, can I try?

I would like to proceed with the following policy.

  • Enable recommended and stylistic, but only enable rules that are the same as the v5 recommended rules.
  • Turn off rules added with stylistic so that they do not affect the roadmap.

I would also like to consider support for #303 and ESLint Flat Config, which will be supported in the future.
If there are no problems, I'd like to submit Pull Request (experiment branch).

@danielroe
Copy link
Member Author

@shinGangan I really appreciate it.

@DamianGlowala has been leading the work on this, so it might be worth waiting for his suggestion on the best way to contribute.

@shinGangan
Copy link
Contributor

Hi @DamianGlowala ( and @danielroe ).

I think that support for eslint-config is not a high priority for the Nuxt core team.
(Thanks for the release of Nuxt 3.9 and the development of many great features 🙏).

However, many nuxt users are confused about eslint-config.

So, if I can help in any way, I would like to help it. It would be helpful if you could share your roadmap when you have time.

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