Find newer versions of dependencies than what your package.json or bower.json allows
npm-check-updates is a command-line tool that allows you to upgrade your package.json or bower.json dependencies to the latest versions, regardless of existing version constraints.
npm-check-updates maintains your existing semantic versioning policies, i.e., it will upgrade your
"express": "^4.11.2" dependency to
"express": "^5.0.0" when express 5.0.0 is released.
Should bower support be part of npm-check-updates or a separate package? We need your input!
npm install -g npm-check-updates
Show any new dependencies for the project in the current directory:
$ ncuexpress 4.12.x → 4.13.xmulter ^0.1.8 → ^1.0.1react-bootstrap ^0.22.6 → ^0.24.0react-a11y ^0.1.1 → ^0.2.6webpack ~1.9.10 → ~1.10.5Run with -u to upgrade your package.json
Upgrade a project's package file:
Make sure your package file is in version control and all changes have been committed. This will overwrite your package file.
$ ncu -uexpress 4.12.x → 4.13.xpackage.json upgraded
Works with bower:
$ ncu -m bower # will use bower.json and check versions in bower
Include or exclude specific packages:
# match mocha and should packages exactly$ ncu mocha,should# match packages that start with "gulp-" using regex$ ncu /^gulp-/# match packages that do not start with "gulp-". Note: single quotes are required# here to avoid inadvertant bash parsing$ ncu '/^(?!gulp-).*$/'
-d, --dev check only devDependencies -e, --error-level set the error-level. 1: exits with error code 0 if no errors occur. 2: exits with error code 0 if no packages need updating (useful for continuous integration) -g, --global check global packages instead of in the current project -h, --help output usage information -j, --jsonAll output new package file instead of human-readable message --jsonUpgraded output upgraded dependencies in json -l, --loglevel what level of logs to report: silent, error, warn, info, verbose, silly (default: warn) --packageData include stringified package file (use stdin instead) --packageFile package file location (default: ./package.json) -m, --packageManager npm or bower (default: npm) -o, --optional check only optionalDependencies -p, --prod check only dependencies (not devDependencies) -r, --registry specify third-party NPM registry -s, --silent don't output anything (--loglevel silent) -t, --greatest find the highest versions available instead of the latest stable versions (alpha release only) -u, --upgrade overwrite package file -a, --upgradeAll include even those dependencies whose latest version satisfies the declared semver dependency -V, --version output the version number
The tool allows integration with 3rd party code:
var ncu = require'npm-check-updates';ncurunpackageFile: 'package.json'// Any command-line option can be specified here.// These are set by default:// silent: true,// jsonUpgraded: truethenconsole.log'dependencies to upgrade:' upgraded;;
1.0.0 < 2.0.0→
^1.0.0 is a range that will includes all non-major updates. If you run
npm update, it will install
1.0.1 without changing the dependency listed in your package file. You don't need to update your package file if the latest version is satisfied by the specified dependency range. If you really want to upgrade your package file (even though it's not necessary), you can run
See the github releases.
For help migrating from v1 to v2, see the v2 release notes.
In some environments (Windows?) npm-check-updates may hang. Run
ncu --loglevel verbose to see if it is waiting for stdin. If so, try setting the package file explicitly:
ncu -g --packageFile package.json. See #136.
If you installed node via brew,
ncu -g may incorrectly report that all packages are up-to-date. Try
PREFIX="/usr/local/" ncu -g. See #146.
Cannot find module 'proto-list'. This error is occurring for many people, yet it cannot be consistently reproduced. It seems to be fixed by fresh installs of node and npm: "I reinstalled node 4.2.1 and npm 2.14.7. Installed ncu, and it worked fine. So I'm afraid I'm not able to reproduce the issue anymore." See #144.
When filing an issue, always include the dependencies from your package file (or the output from
npm -g ls --depth=0 if using global mode)!
Pull requests are welcome, and will not collect dust :)