-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
False positive: eslint-config-prettier #330
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
rumpl
added a commit
that referenced
this issue
Nov 3, 2019
rumpl
added a commit
that referenced
this issue
Nov 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
This might be too much to expect depcheck to handle, but eslint-config-prettier is used by eslint-plugin-prettier when the ESLint config includes
{ "extends": ["plugin:prettier/recommended"] }
, even though eslint-plugin-prettier'spackage.json
only includes eslint-config-prettier as a dev dependency. (See Prettier's documentation on integrating with ESLint.) When runningdepcheck --specials=eslint
, though, eslint-config-prettier is listed as an unused dev dependency, though it is actually a dev dependency.(This seems different than #316 where the issue was eslintConfig not being honored in the package.json.)
Code snippets
Where the dependency is used:
Where the dependency is listed in package.json:
Versions
node -v
: v8.12.0npm -v
: 6.4.1depcheck --version
: 0.7.2Extra info
Here's the output of
depcheck --json --specials=eslint
(with the"using"
paths obscured):Thanks for any help you can provide, and for your work on this package.
The text was updated successfully, but these errors were encountered: