Used package classed as unused
See original GitHub issueI’m working on a fork for babel and noticed that it classified lodash
as “NOTUSED?” when the codebase did have require("lodash/...")
and import ... from "lodash/..."
which makes me think that this package doesn’t take into account when a dependency is used indirectly.
Is there a way to fix that?
Issue Analytics
- State:
- Created 5 years ago
- Comments:9
Top Results From Across the Web
Find unused npm packages in package.json - Stack Overflow
You can use an npm module called depcheck (requires at least version 10 of Node). Install the module: npm install depcheck -g or...
Read more >How to Check if You Have Unused Dependencies in Your ...
Npm-check's job is to check if your packages are all up-to-date and in use. This package provides a beautiful summary of the packages...
Read more >Peer dependencies still showing as "unused" after being ...
If I've installed a package because of peer-dependency ... to X which X has peerDependencies to Y . Both of them will be...
Read more >How do you list unused electronics in a shelf worn package?
Used - Very Good: A well-cared-for item that has seen limited use but remains in great condition. The item is complete, unmarked, and...
Read more >Item condition by category - eBay
Brand new: The book is new, unread, and unused in perfect condition with no ... The item may be missing original packaging and...
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
@Berkmann18 I just cloned your repo and ran
depcheck
in thepackages/babel-cli
directory and I get this:depcheck
shows correctly thatbabel-cli
usesrimraf
intest/index.js
but doesn’t list it as a dependency in itspackage.json
file.Note that depcheck doesn’t support monorepos, you need to run it for each package.
For now, perhaps, I haven’t used this functionality since so it might still be an issue.