npm-check ========= [](https://travis-ci.org/dylang/npm-check) [](http://badge.fury.io/js/npm-check) []()
Check for outdated, incorrect, and unused dependencies.
<img width="796" alt="npm-check -u" src="https://cloud.githubusercontent.com/assets/51505/9569917/96947fea-4f48-11e5-9783-2d78077256f2.png"
Features
- Tells you what's out of date.
- Provides a link to the package's documentation so you can decide if you want the update.
- Kindly informs you if a dependency is not being used in your code.
- Works on your globally installed packages too, via -g.
- Interactive Update for less typing and fewer typos, via -u.
- Supports public and private @scoped/packages.
- Supports ES6-style import from syntax.
- Upgrades your modules using your installed version of npm, including the new npm@3, so dependencies go where you expect them.
- Works with any public npm registry, private registries, and alternate registries like Sinopia.
- Does not query registries for packages with private: true in their package.json.
- Emoji in a command-line app, because command-line apps can be fun too.
- Works with npm@2 and npm@3, as well as newer alternative installers like ied and pnpm.
Requirements
- Node = 10.9.0
On the command line
This is the easiest way to use npm-check.
Install
npm install -g npm-checkUse
npm-check<img width="882" alt="npm-check" src="https://cloud.githubusercontent.com/assets/51505/9569919/99c2412a-4f48-11e5-8c65-e9b6530ee991.png"
The result should look like the screenshot, or something nice when your packages are all up-to-date and in use.
When updates are required it will return a non-zero response code that you can use in your CI tools.