Releases · raineorshine/npm-check-updates

Newer published versions that satisfy the specified range are not upgraded by default (e.g. 1.0.0 to 1.1.0). This change was made because npm update handles upgrades within the satisfied range just fine, and npm-check-updates is primarily intended to provide functionality not otherwise provided by npm itself. These satisfied dependencies will still be shown when you run npm-check-updates, albeit with a short explanation. For the old behavior, add the -ua/--upgradeAll option.
The command-line argument now specifies a package name filter (e.g. ncu /^gulp-/). For the old behavior (specifying an alternative package.json), pipe the package.json through stdin.
Use the easier-to-type ncu instead of npm-check-updates. npm-check-updates is preserved for backwards-compatibility.

Changelog

Allow packageData to be specified as an option
Colored table output
Add -a/--upgradeAll
Add -e/--error-level option
Add -j/--json and --jsonFlat flags for json output
Add -r/--registry option for specifying third-party npm registry
Add -t/--greatest option to search for the highest versions instead of the default latest stable versions.
Remove -f/--filter option and move to command-line argument
Replace < and <= with ^
Automatically look for the closest descendant package.json if not found in current directory
Add ncu alias
Export functionality to allow for programmatic use
Bug fixes and refactoring
Full unit test coverage!

Assets 2

14 Aug 17:55

v1.5.1

Assets 2