-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat: support ESLint v9 #9002
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: support ESLint v9 #9002
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Awesome! LGTM 🏆
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.
question: do we really want to do the bump to v9 if it completely breaks our lint setup like this?
would we be better served by instead just adding a decent integration test which runs against v9, and leaving our setup on v8 for now?
packages/eslint-plugin/tests/rules/no-unused-vars/no-unused-vars-eslint.test.ts
Show resolved
Hide resolved
packages/integration-tests/tests/__snapshots__/flat-config-types.test.ts.snap
Outdated
Show resolved
Hide resolved
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.
I ran yarn dedupe
to trim this file down a bit. Then I reverted the tmp
upgrades as they cause a few odd CI failures. #8589
This comment has been minimized.
This comment has been minimized.
Now that this is merged, the If you still have problems with typescript-eslint and ESLint v9:
Note that we do not plan on backporting ESLint v9 support to v7 versions of typescript-eslint. There are a lot of breaking changes inherent to our ESLint v9 support. If any enterprising individual wants to try onboarding us in typescript-eslint to ESLint v9, #9082 tracks that as a followup. |
PR Checklist
Overview
Keeps us on ESLint v8 internally, but adds v9 to the supported version ranges. Adds a CI check that
yarn add eslint@9; yarn test
passes.