chore: migrate eslint-plugin-import
to eslint-plugin-import-x
#11217
+1,632
−982
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
eslint-plugin-import
toeslint-plugin-import-x
#11212Overview
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