Number of watchers on Github | 1886 |
Number of open issues | 16 |
Average time to close an issue | about 1 month |
Main language | JavaScript |
Average time to merge a PR | 3 days |
Open pull requests | 6+ |
Closed pull requests | 1+ |
Last commit | over 1 year ago |
Repo Created | over 3 years ago |
Repo Last Updated | 12 months ago |
Size | 1.3 MB |
Organization / Author | peerigon |
Latest Release | v2.0.0 |
Contributors | 4 |
Page Updated | 2018-03-12 |
Do you use updtr? Leave a review! | |
View open issues (16) | |
View updtr activity | |
View on github | |
Fresh, new opensource launches πππ | |
Trendy new open source projects in your inbox!
View examples
|
Update outdated npm modules with zero pain
Based on npm outdated
, updtr installs the latest version and runs npm test
for each dependency. In case the test succeeds, updtr saves the new version number to your package.json
. Otherwise, updtr rolls back the conflicting update.
Additionally, it will use yarn
instead of npm
when a yarn.lock
file is present in your project.
Made by Peerigon.
npm install -g updtr
--use
-u
Specify the package manager to use:
npm
yarn
Updtr tries to guess the package manager by looking for a yarn.lock
file. If there is one in process.cwd()
, it will use yarn. Setting this option overrides that default.
--exclude
--ex
Space separated list of module names that should not be updated.
--update-to
--to
latest
(default): update all packages to the latest version numbernon-breaking
: update all packages to the latest version number that does not conflict with the installed version numberwanted
: update all packages to the latest version number that does not conflict with the version number as specified in the package.json
--save
-s
Specify how updated versions should be saved to the package.json
:
smart
(default): tries to preserve the current style. Falls back to caret
if the style cannot be preserved.caret
: saves ^x.y.z
exact
: saves x.y.z
--reporter
-r
Choose a reporter for the console output:
dense
(default): See screenshotnone
: No console output--test
-t
Specify a custom test command. Surround with quotes:
updtr -t "mocha -R spec"
--test-stdout
--out
Show test stdout if the update fails.
--registry
--reg
Specify a custom registry to use.
Please note: yarn does not support to set a custom registry via command line. Use a .npmrc
file to achieve this. See also yarnpkg/yarn#606.
--version
Show the current updtr version.
--help
Show all commands.
Unlicense
--use, -u Specify the package manager to use [choices: "npm", "yarn"] [default: "npm"]
--exclude, --ex Space separated list of module names that should not be updated [array]
--update-to, --to Specify which updates you want to install [choices: "latest", "non-breaking", "wanted"] [default: "latest"]
--save, -s Specify how updated versions should be saved to the package.json [choices: "smart", "caret", "exact"] [default: "smart"]
--reporter, -r Choose a reporter for the console output [choices: "dense", "none"] [default: "dense"]
--test, -t Specify a custom test command. Surround with quotes.
--test-stdout, --out Show test stdout if the update fails [boolean]
--registry, --reg Specify a custom registry to use
--version Show version number [boolean]
--help Show help [boolean]