Package Exports
- npm-up
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (npm-up) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
npm-up
A lightweight tool to check the latest version of dependent npm packages for a project and do whatever you want.
Installation
npm i npm-up -g
Usage
run npm-up [options] in a project directory with a package.json file.
For example: npm-up -ab
If no options are set, it will only check the latest version and do nothing but display.
####Options:
-h, --help output usage information
-v, --ver Display the current version of npm-up
-g, --global Check global packages
-w, --writeback Write updated version info back to package.json
-i, --install Install the newest version of the packages that need to be updated.
-l, --lock Lock the version of the package in package.json, with no version prefix.
-a, --all alias for -wil.
-b, --backup [fileName] BackUp package.json before write back, default is package.bak.json.
-d, --dep Check dependencies only.
-D, --dev Check devDependencies only.
-s, --silent Do not log any infomation.
-e, --exclude <list> Excluded packages list, split by comma
-o, --only <list> Only check the packages list, split by commaVersion Pattern
Only support number version with prefix and suffix, or *. Eg:
*
^1.5.4
~2.3
0.9.7
>=0.9.8
0.5.0-alpha1- However, the semantic meaning of the prefix and suffix is ignored, because I just want the latest version.
- If the version declared in the
package.jsonis not recognizable, the corresponding package will be excluded.
Rules
- Take 3 versions into consideration:
- Version declare in
package.json - Version of the package installed
- The latest version of the package
- Version declare in
- If a package is not installed, only
package.jsonwill be updated, and the package itself won't be installed. - If the version is
*inpackage.json, it will never be overwritten, even the flaglockis set. - The preifx of the version will be preserved when write back, unless flag
lockis set. - If the version installed is not the same as the version declared in
package.json, there comes a warning. - Installed version is preferred.
How to build
cake build