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 -gUsage
Run
npm-up [options]in a project directory with apackage.jsonfile. For example:npm-up -iw.
If no options are configured, it will only check the latest version and do nothing but display.Run
npm-up -gto check globally install npm packages.Run
npm-up -Ato check all projects in sub directories.
commands:
clean clean cache
dump dump cacheOptions:
-h, --help output usage information
-V, --version output the version number
-g, --global Check global packages.
-A, --All Check all projects in sub directories, depth is 1.
-w, --writeBack Write updated version info back to package.json.
-i, --install Install the latest version of the packages need to be updated.
-l, --lock Lock the version of the package in package.json, with no version prefix.
--lock-all Lock, even with * version.
-a, --all Shortcut for -wil.
-m, --mirror <mirror host or name> Use a mirror registry server.
--no-cache Disable version cache.
--no-warning Disable warning.
-b, --backup [fileName] Back up package.json before writing back, default name is package.bak.json.
-d, --dep Check dependencies only.
-D, --dev Check devDependencies only.
-s, --silent Do not print any infomation.
-c, --cwd <cwd> Current working directory.
-L, --logLevel <level> Set loglevel for npm, default is error
-e, --exclude <list> Excluded packages list, split by comma or space.
-o, --only <list> Included packages list, split by comma or space.Use mirror registry
First of all, You are supposed to use something like
npm config set registry http://registry.npm.taobao.orgto set a npm registry globally if necessary.
However, if you don't want to do this, you can do this only in npm-up.
You can use a mirror registry host to speed up the version searching and package downloading, especially for Chinese users.
- You can use a built-in host with name:
- support: taobao, cnpmjs, npm(official), skimdb
npm-up -m taobao- or give a specific hostname (only allow
httpnow)
npm-up -m registry.npm.taobao.orgFor Chinese users, use
-m taobaoto fly up!
Version Pattern
Fully support semantic version. Eg:
*
^1.5.4
~2.3
0.9.7
0.5.0-alpha1
'' //regard as *Notice that ranges version may be overridden by Caret Ranges(^) when written back, and will be updated only when the latest version is greater than all the versions possible in the range.
>= 1.0.0 <= 1.5.4 // Version Range
1.2 - 2.3.4 // Hyphen Ranges
1.x // X-Ranges- However, the semantic meaning of the prefix and suffix may somehow ignored, because I just want the latest version.
- If the version declared in the
package.jsonis not recognizable, the corresponding package will be excluded. - More info: https://docs.npmjs.com/misc/semver
Rules
Take 3 versions into consideration for one package:
- Version declared in
package.json. - Version of the package installed.
- The latest version of the package.
- Version declared 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 not be overwritten, even when the flaglockis set. If you really want to change a*version, use--lock-allflag.The prefix
^ ~of the version will be preserved when written back, unless flaglockis set.If an installed package's version is not the same as the version declared in
package.json, there comes a warning.Installed version is preferred.
Roadmap
- Use a config file to provide some persist options, like npmrc, we can have a real npmuprc.
License
MIT