pgilad/grunt-dev-update

Issues

• Dependency Security Vulnerability [Low]

  #31 opened 5 years ago by EvanHerman
  1

• updating outdated packages doesn't update the package.json

  #28 opened 8 years ago by luca-borrione
  1

• error with node@6

  #27 opened 8 years ago by diggy
  4

• When new packages are available, devUpdate stops with error

  #26 opened 8 years ago by philwareham
  2

• choosing "no" aborts

  #23 opened 9 years ago by boneskull
  0

• Problems in Jenkins when there is no TTY attached

  #21 opened 10 years ago by goloroden
  1

• Support and parse GitHub dependencies

  #18 opened 10 years ago by goloroden
  5

• Warn / error if current version does not match wanted version

  #20 opened 10 years ago by goloroden
  1

• GitHub dependencies exclusion does not work

  #19 opened 10 years ago by goloroden
  1

• Skip update/install when not needed

  #15 opened 10 years ago by vkadam
  2

• "fail" updateType and "skip" options

  #13 opened 10 years ago by lukemadera
  9

• Add ignoredPackages option

  #14 opened 10 years ago by pgilad
  0

• feature request - bower support

  #11 opened 11 years ago by Kikobeats
  5

• problem with prompt when multiple packages are outdated

  #10 opened 11 years ago by pgilad
  0

• parse.JSON "Error in JSON.parse of the local package info of xxx"

  #7 opened 11 years ago by morriswchris
  6

• Add some kind of caching?

  #6 opened 11 years ago by voxpelli
  4

• Switch to using npm outdated for getting local/remote/wanted versions

  #8 opened 11 years ago by pgilad
  0

• Option to check for latest compatible update

  #5 opened 11 years ago by voxpelli
  1

• No waiting for user output in some cases...

  #3 opened 11 years ago by pgilad
  1

• finding package.json isn't working, if you leave it null - it will use grunt devUpdate package.json

  #4 opened 11 years ago by pgilad
  1

• [FEATURE] : Read plugin's changelog before updating

  #1 opened 11 years ago by wildeyes
  1