Issues filed for peerigon/updtr

View Full Project
Do you use updtr? Leave a review!

Rate of open issues in the last 60 days

updtr open issues (View Closed Issues)
  • over 2 years Yarn Support
  • over 2 years doesn't work with linked modules
  • over 2 years update prerelease versions
  • over 2 years Update dependencies with peerDependencies at the end
  • over 2 years Updtr changes the specifity defined in `package.json`
  • over 2 years Don't update package.json if latest version is included in version range
  • over 2 years Use `engines` field to avoid breaking changes.
  • almost 3 years Use binary search to find the failing packages faster?
  • over 3 years Is pain trademarked?
  • over 3 years Keep the same rule for the versions instead of forcing ^
  • over 3 years devDependencies are saved as dependencies
  • over 3 years Allow updtr to skip certain dependencies?

updtr closed issues

  • over 2 years Fail using npm@4.0.1
  • over 2 years Report name of missing modules
  • almost 3 years prevent downgrading to stable version when package.json specifies a pre-release version
  • almost 3 years not Updating packages on node 6
  • almost 3 years Trouble rolling back
  • almost 3 years unfortunate, handling error with beta / next modules
  • about 3 years update dependencie fails
  • about 3 years Simple reporter option
  • about 3 years Every time I run updtr it says it's updating nock from 7.2.2 to 7.2.2
  • about 3 years rvm not recognized as internal command on Windows 10
  • about 3 years Add option to specific custom npm registry
  • about 3 years Keep formatting in package.json
  • over 3 years Fails when dependency not installed
  • over 3 years downgrades version to @latest
  • over 3 years Is it possible to get the output (stdout/stderr) from the npm test command?
  • over 3 years Causes invalid peer dependencies
  • over 3 years Updtr failed
  • over 3 years Don't update to beta releases