Unnecessary dependencies on package.json when installing
See original GitHub issueEven thought most of these dependencies were on my devDependencies, yarn add it to yarn.lock and node_modules:
"dependencies": {
"babel-core": "^6.25.0",
"babel-loader": "^7.1.1",
"babel-runtime": "^6.23.0",
"prop-types": "^15.5.10",
"webpack": "^3.3.0"
},
I believe most of those dependencies should be a devDependency and prop-types is not a dependency, since you use flow
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 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 >Remove unused npm modules from package.json
Remove unused npm modules from package.json ... Depcheck is a tool for analyzing the dependencies in a project to see: how each dependency...
Read more >How to Check if You Have Unused Dependencies in Your ...
Solution 1. depcheck ; npm install -g depcheck. Second, launch the dependency analyzer simply by: ; depcheck. Third, check the unused dependencies ......
Read more >Remove unused dependencies from package.json #16840
While working on #16453 I ran npx depcheck to look for unused dependencies, and the result is npx: installed 146 in 6.204s Unused...
Read more >How to check unused npm packages? - Mario Kandut
Best practice is to remove unused code. Use tools like depcheck or npm-check to find unused dependencies. Thanks for reading and if you...
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
Should be fixed in 1.1.0!
Whoops! I probably just forked another OSS project I had to create this one and wasn’t careful about cleaning up dependencies. That or I forgot the
--dev
flag whenyarn add
ing some.Either way, sorry. I’ll tidy up before the next release.