-
-
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
Exclude package main files by default from no-unused-modules
#1327
Labels
Comments
ehmicky
changed the title
[ENHANCEMENT] Exclude
[ENHANCEMENT] Exclude package main files by default from Apr 14, 2019
package.json
main
file by default from no-unused-modules
no-unused-modules
ehmicky
changed the title
[ENHANCEMENT] Exclude package main files by default from
Exclude package main files by default from Apr 14, 2019
no-unused-modules
no-unused-modules
That sounds like a good enhancement, no need for it to be behind an option, even. |
What package.json should be used for this purpose?
|
For a given file, the closest package.json to it, that has a main, does not have private true, and points to it, marks it as used. |
ljharb
pushed a commit
to rfermann/eslint-plugin-import
that referenced
this issue
Jul 17, 2019
ljharb
pushed a commit
to rfermann/eslint-plugin-import
that referenced
this issue
Jul 17, 2019
Thanks for implementing this @ljharb! 🎉 |
Thank @rfermann :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
unusedExports: true
with theno-unused-modules
rule should never report files that are exported as the main file (main
,browser
orbin
fields inpackage.json
). What do you think?The text was updated successfully, but these errors were encountered: