-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: migrate eslint-plugin-import
to eslint-plugin-import-x
#11217
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
Conversation
Thanks for the PR, @JounQin! 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 project configuration. |
View your CI Pipeline Execution ↗ for commit 9370841.
☁️ Nx Cloud last updated this comment at |
I don't know, Update: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11217 +/- ##
=======================================
Coverage 90.84% 90.84%
=======================================
Files 501 501
Lines 50919 50919
Branches 8387 8387
=======================================
Hits 46256 46256
Misses 4648 4648
Partials 15 15
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
fc1ebc7
to
36cf5b1
Compare
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.
The perf boost is nice, but there are a lot of lockfile & package dep changes that are not needed for this. Could you please revert any that aren't actually necessary / newly caught issues (e.g. the Docusaurus 3.7 bump)?
I think we need a relatively clean PR showing that the lockfile doesn't get significantly larger from this change. #11212 (comment) raises a good point that we already have a lot of deps from multiple plugins in this package. The size of node_modules is a performance factor for us too (#11204). I think we'd want to know how "bad" the duplication is before making the switch-or-not call.
Thanks for getting this to a reviewable state. Seeing the lockfile and having a clean slate to run performance measurements locally on was helpful. Conclusions commented here: #11212 (comment) tl;dr: this won't be a net positive unless & until the other I'll go ahead and close this out to keep the queue small. Looking forward to being able to reevaluate later this year though! 💙 |
@@ -53,6 +53,9 @@ | |||
"@typescript-eslint/types": "^8.35.0", | |||
"debug": "^4.3.4" | |||
}, | |||
"devDependencies": { | |||
"vitest": "^3.1.3" |
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.
@JoshuaKGoldberg By the way, this is found by import-x
.
And also #11265
PR Checklist
eslint-plugin-import
toeslint-plugin-import-x
#11212Overview
Old measurements (see later for updated ones)
Before:For a single ESLint plugin migration, I believe from 1m13s to 1m8s is already good enough, and it founds a false positive that
@docusaurus/plugin-content-blog
should be listed independencies
forwebsite
, becauseeslint-plugin-import-x
is a TypeScript rewrite started at un-ts/eslint-plugin-import-x#42 and we fixed several hidden bugs thanks to TypeScript!(I don't know why
nx
complains aboutreact-helmet-async
version incompatible with@docusaurus/core
's, see also https://app.unpkg.com/@docusaurus/core@3.7.0/files/package.json#L63, so I'm locking it same way to makenx
happy.)cc @JoshuaKGoldberg