-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[no-unused-modules] Error with ESLint configuration non-standard name #2678
Comments
This seems like an issue with eslint itself, and not with eslint-plugin-import - this plugin doesn't do anything with eslint config. (typically you'd only ever have one eslint config file in any repo, at the root, and you'd use |
@ljharb I created an issue at ESLint and eslint-plugin-import use indirectly ESLint config:
|
Yes, everything uses it indirectly - the bug is only with something that uses it directly. |
Reopening per the comment on the linked issue. |
This also seems to be an issue with the new eslint flat config file. When I enable this rule, I get the message:
Flat config is in the root directory of the project, with no |
The
import/no-unused-modules
rule doesn't work when the ESLint configuration file doesn't have a standard name. In my projects, I group the configuration files in a directory to avoid having too many files in the root (example with Cast Kodi).index.js
my_eslint.json
package.json
Run this command:
npx eslint -c my_eslint.json index.js
The text was updated successfully, but these errors were encountered: