Want to take your software engineering career to the next level? Join the mailing list for career tips & advice Click here
Statistics on updtr
| Number of watchers on Github | 2190 |
| Number of open issues | 15 |
| Average time to close an issue | about 1 month |
| Main language | JavaScript |
| Average time to merge a PR | 2 days |
| Open pull requests | 9+ |
| Closed pull requests | 2+ |
| Last commit | almost 2 years ago |
| Repo Created | almost 5 years ago |
| Repo Last Updated | 27 days ago |
| Size | 1.66 MB |
| Organization / Author | peerigon |
| Latest Release | v3.1.0 |
| Contributors | 4 |
| Page Updated | 2020-07-20 |
| Do you use updtr? Leave a review! | |
| View open issues (15) | |
| View updtr activity | |
| View on github | |
| Book a Mock Interview With Me (Silicon Valley Engineering Leader, 100s of interviews conducted) | |
|
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
|
|
updtr
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.
Installation
npm install -g updtr
Options
--use -u
Specify the package manager to use:
npmyarn
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 number -
non-breaking: update all packages to the latest version number that does not conflict with the installed version number -
wanted: update all packages to the latest version number that does not conflict with the version number as specified in thepackage.json
--save -s
Specify how updated versions should be saved to the package.json:
-
smart(default): tries to preserve the current style. Falls back tocaretif the style cannot be preserved. -
caret: saves^x.y.z -
exact: savesx.y.z
--reporter -r
Choose a reporter for the console output:
-
dense(default): See screenshot -
basic: Usesconsole.logfor output, no need for a TTY (e.g when running on CI) -
none: 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.
License
Unlicense
Sponsors
- almost 4 years Yarn Support
- almost 4 years doesn't work with linked modules
- almost 4 years update prerelease versions
- almost 4 years Update dependencies with peerDependencies at the end
- almost 4 years Updtr changes the specifity defined in `package.json`
- almost 4 years Don't update package.json if latest version is included in version range
- almost 4 years Use `engines` field to avoid breaking changes.
- about 4 years Use binary search to find the failing packages faster?
- over 4 years Is pain trademarked?
- over 4 years Keep the same rule for the versions instead of forcing ^
- over 4 years devDependencies are saved as dependencies
- over 4 years Allow updtr to skip certain dependencies?
- Simple reporter
- Report the names of missing modules
- Rewrite
- Support for yarn outdated multiline stdout
- fix: yarn parse
- feat: add basic reporter
- Dependency updates
- [Feature] Interactive update
- fix: parse Yarn JSON on any OS
v3.1.0 v3.1.0
v3.0.0 v3.0.0
Bug Fixes
Fix
- Stdout output parsing from yarn (ff56fbb)
BREAKING CHANGES
- Removed official Node 4 support. It may still work, but now you're on your own.
v2.0.0 v2.0.0
Features
BREAKING CHANGES
- New and changed CLI options
--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]