Add note(s) to docs about flat configs and/or no-unused-modules' `unusedExports` not being supported in flat configs about eslint-plugin-import HOT 5 OPEN

Given that eslint's FlatCompat allows people to use this plugin before it actually supports flat config, I agree adding a note in the readme (linked to from the no-unused-modules docs) here would be good.

from eslint-plugin-import.

I'm not using the no-unused-modules rule directly, but I am attempting to bundle my ESLint flat config that includes eslint-plugin-import using rollup.

Of all the plugins & rules I'm using, no-unused-modules is the only one that's giving me trouble:

(!) Plugin node-resolve: Could not resolve import "eslint/lib/cli-engine/file-enumerator" in /Users/jzwartepoorte/Projects/components/node_modules/eslint-plugin-import/lib/rules/no-unused-modules.js using exports defined in /Users/jzwartepoorte/Projects/components/node_modules/eslint/package.json.
(!) Plugin node-resolve: Could not resolve import "eslint/lib/util/glob-utils" in /Users/jzwartepoorte/Projects/components/node_modules/eslint-plugin-import/lib/rules/no-unused-modules.js using exports defined in /Users/jzwartepoorte/Projects/components/node_modules/eslint/package.json.
(!) Plugin node-resolve: Could not resolve import "eslint/lib/util/glob-util" in /Users/jzwartepoorte/Projects/components/node_modules/eslint-plugin-import/lib/rules/no-unused-modules.js using exports defined in /Users/jzwartepoorte/Projects/components/node_modules/eslint/package.json.

My next step is trying to exclude this rule somehow from bundling.

from eslint-plugin-import.

I’m not sure why you’d ever want to bundle an eslint config - and either way, this plugin requires everything to exist on disk to work properly, so it’s not going to work with that approach.

from eslint-plugin-import.

I'm trying to create a zero dependency ESLint config, which hopefully speeds up ESLint's running time significantly.

As far as I can tell, the paths that node-resolve complains about don't exist?!

from eslint-plugin-import.

That seems like a really bizarre way to solve it; I'd suggest using jest-eslint-runner instead, it does the job without violating the expectations of basically every package.

It seems like the error is coming from your rollup setup - the paths don't necessarily exist, which is why they're being conditionally required in the first place.

from eslint-plugin-import.