-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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: ESLint v9 Support #7543
feat: ESLint v9 Support #7543
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit c746f3f. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit c746f3f:
|
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.
Thank you 🙏 . Is this fully backwards compatible? Do we need to change the docs for users using the flat / legacy configs?
please also update eslint in the examples. It would serve as a good reference point to see if things are still working |
I am not aware flat config could be used before. We could update the docs to say that ESLint v9 is supported with In my test repo this was a non-breaking update with the following setup: "@typescript-eslint/eslint-plugin": "7.8.0",
"@typescript-eslint/parser": "7.8.0",
"eslint": "8.57.0",
"eslint-import-resolver-typescript": "3.6.1",
"eslint-plugin-import": "2.29.1",
"eslint-plugin-jest": "27.9.0",
"eslint-plugin-react": "7.34.1",
"eslint-plugin-react-hooks": "4.6.2", I installed the updated plugin from file after running |
okay thanks, so this is just for v9 support, not for flat config support? |
I tried to create a new example at first, but I was unsure on how to reference the plugin updates I had to do because the other examples were referencing published package versions. I created this repo https://github.com/davidjbng/eslint-plugin-query-v9-example which is just a copy of basic-typescript with eslint v9 config |
Yes. I opened a new issue for Flat Config here: #7544 |
okay the error that is left is from I did that here: a42a2ed |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7543 +/- ##
==========================================
+ Coverage 43.79% 43.85% +0.06%
==========================================
Files 183 184 +1
Lines 7021 7025 +4
Branches 1535 1539 +4
==========================================
+ Hits 3075 3081 +6
+ Misses 3580 3578 -2
Partials 366 366 |
alright, let' ship it |
FYI getting the below peer-dependency warning with this release. @TkDodo @davidjbng I think the peer definition should either be |
yes, someone please fix it. It should be:
just like we have for react:
|
Working on the fix. Seems like npm fails to report peerDependency errors when installing from a file path. I found at least a few similar issues like this: |
Closes #7286
This PR adds support for ESLint v9 and is backwards compatible with ESLint v8.
I upgraded to the @typescript-eslint v8 alpha packages which support ESLint v9, but that required some type changes.
It is mostly the same as proposed in #7253 but does not yet support the flat config format. I will create a separate tracking issue for that.
Tests
To Be Discussed
Docs
I did not update any docs yet because there are basically no configuration changes required to use v9.
Flat config will be more important to document once it is supported.