-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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: use eslint 9 #9119
base: v8
Are you sure you want to change the base?
feat: use eslint 9 #9119
Conversation
Thanks for the PR, @abrahamguo! 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. |
We should delete this CI job typescript-eslint/.github/workflows/ci.yml Lines 137 to 154 in 87a0a48
have we got an existing integration test to check for regressions on eslint v8? converting to draft until CI is passing. |
@bradzacher there are currently no integration or CI tests for eslint 8. I can add one if you want, but do you feel that's necessary since we ask for eslint 9 in both our peerDependencies and devDependencies? Doesn't seem like anything similar was added for eslint 7 when we moved from eslint 7=>8 (#3737) Also, seems unrelated to this PR since this is about using eslint 9 internally |
Looks like there's already an integration test for v8 - https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/integration-tests/fixtures/eslint-v8
By moving to v9 internally our CI is no longer running against v8 - so we lose the test coverage asserting that we don't regress v8 compat. But given we have the above integration test - we still have enough coverage. |
Just wanted to point out that one of your Netlify jobs has been running for nearly a week. |
@mattbrannon that's nothing compared to #8673, whose job has been running for 3 weeks 😉 It does seem like that specific job sometimes hangs indefinitely. Not sure why |
Note: The typescript eslint plugin isn't ready for eslint v9 yet, so we need to keep it at v8 for now See: typescript-eslint/typescript-eslint#9119
Note: The typescript eslint plugin isn't ready for eslint v9 yet, so we need to keep it at v8 for now See: typescript-eslint/typescript-eslint#9119
Note: The typescript eslint plugin isn't ready for eslint v9 yet, so we need to keep it at v8 for now See: typescript-eslint/typescript-eslint#9119
['deprecation']: deprecationPlugin, | ||
// https://github.com/gund/eslint-plugin-deprecation/issues/85 | ||
// https://github.com/typescript-eslint/typescript-eslint/issues/8988 | ||
['deprecation']: fixupPluginRules(deprecationPlugin), |
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.
TODO: looks like this got fixed — try it out
PR Checklist
Overview
Use eslint@9 internally.