Installed peer dependencies are marked as unused
See original GitHub issueFor example, babel-core
is a peer dependency of babel-loader
. It should not be marked as unused. The same goes for jasmine-core
and karma-jasmine
.
There are probably many more similar cases.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Find unused npm packages in package.json - Stack Overflow
Install the module: npm install depcheck -g or yarn global add depcheck. Run it and find the unused dependencies: depcheck.
Read more >How to fix npm dependency hell - Sylhare's blog
This will do a clean installation of the modules, removing the previous node modules and won't try to update the dependencies (which can...
Read more >npm Peer Dependencies - Fathom
When you use peer dependencies, npm will not automatically install those dependencies (see comments above in respect to npm version 7). This can...
Read more >eslint-plugin-unused-imports - npm
eslint-plugin-unused-imports. 2.0.0 • Public • Published a year ago. Readme · Code Beta · 1 Dependency · 339 Dependents · 17 Versions ...
Read more >Error Codes | Yarn - Package Manager
The author of packageB can fix this problem by marking the packagePeer peer dependency as optional - but only if the peer dependency...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This still appears to be happening. My project has a peer dependency on
prom-client
:However,
depcheck
lists it as unused after installation:It works! Thanks 😄