cleaner dependencies and supports exports better

I believe you, but can you back this up please? 🙂

As in: I'm totally on board with e18e initiatives, just we need details before jumping onto something new.

• Cleaner dependencies: what's different? what's the new dep tree? how does that look in this repo, given its other devDeps?
• Supports exports better: what does that mean? How does that practically impact us?

@JoshuaKGoldberg Sorry for the confusing, I definitely should add a Why or Different with eslint-plugin-import section in README: un-ts/eslint-plugin-import-x#196, before that lands, just quote from another PR: shlinkio/js-coding-standard#129 (comment), see also un-ts/eslint-plugin-import-x#24.

Supports exports better: what does that mean? How does that practically impact us?

Could be no issue here for tseslint but eslint-plugin-import itself: import-js/eslint-plugin-import#2703, whenever tseslint adds/updates a dependencies only provide exports field, there will be an issue then.

Those are good links, thanks. My vote is to mark this as blocked on having actual benchmarks / metrics showing why eslint-plugin-import-x would be better for our use case.

I hope+think this should be a pretty straightforward blocker to resolve:

• docs: add Why or Different with eslint-plugin-import in readme un-ts/eslint-plugin-import-x#196: someone writing up those docs
• feat: migrate to import-x with lighter deps and better performance shlinkio/js-coding-standard#129 (comment): running linting benchmarks to show the perf difference on this repo

I'll run a benchmark for you by preparing a PR for it.

@JoshuaKGoldberg Here we go: #11217

eslint-plugin-import-x is a modern fork of eslint-plugin-import with cleaner dependencies

While that's true, this repo unfortunately wouldn't benefit much unless eslint-plugin-jsx-a11y is also switched for another plugin as it pulls in the same set of dependencies: http://npmgraph.js.org/?q=eslint-plugin-jsx-a11y

While that's true, this repo unfortunately wouldn't benefit much unless eslint-plugin-jsx-a11y is also switched for another plugin as it pulls in the same set of dependencies

That's unfortunate https://github.com/es-tooling/eslint-plugin-jsx-a11y-x is only a placeholder package now, I may offer some help when I'm free enough.

And I don't think we should migrate all at once, zero vs all.

@JoshuaKGoldberg For the document part, please help to review un-ts/eslint-plugin-import-x#323.