[REPLACE] eslint-plugin-import → eslint-plugin-import-x

[lishaduck]

Neither one supports ESLint 9.
However, eslint-plugin-import-x is (subjectively) easier, (objectively) lighter weight, and (likely) faster.
I propose migrating, slapping a fixupPluginRules on it, and praying it works.

[AndreaPontrandolfo]

Heh, i'm kind of conflicted on this one.
After the work done in #208 and #219, all of our 7 eslint-plugin-import rules are now working correctly in ESLint v9.
I'm not exactly sure what tangible value eslint-plugin-import-x would provide for us right now.

I'll leave this issue up, so we track the progress of eslint-plugin-import-x and if it really get substantially ahead of eslint-plugin-import in some significative way, we'll make the switch.

[lishaduck]

Oh, import-x merged ESLint 9/TSESLint 8 compat (not yet released though).
We don't need to fix what ain't broke, but just an fyi.

[AndreaPontrandolfo]

Blocked by:

• New resolver design un-ts/eslint-plugin-import-x#40
• import-x/no-default-export does not work in typescript un-ts/eslint-plugin-import-x#144
• fail positives with "no-named-as-default" un-ts/eslint-plugin-import-x#128
• Add option for no-rename-default to exclude some modules un-ts/eslint-plugin-import-x#136
• add eslint-import-resolver-typescript as a dependency un-ts/eslint-plugin-import-x#150

[lishaduck]

Blocked on those other issues before considering this, but Sukka mentioned this in the last link: https://github.com/9romise/eslint-import-resolver-oxc
Looks sweet, if we do switch we might consider swapping out the resolver too.

[AndreaPontrandolfo]

I tested it. It is indeed 10X faster. But it's a very young project, so it's probably not worth it to switch now, too many things that could go wrong.
It's probably just better to wait for un-ts/eslint-plugin-import-x#150 and un-ts/eslint-plugin-import-x#40 and see if they implement it under-the-hood themselves.