Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Discover newer versions of dependencies than package.json allows #1638

wants to merge 4 commits into


None yet
6 participants

The reference issue is isaacs#1428

Newer packages are looked for when issuing a npm outdated on the project.
If a newer package is discovered then there are two options, basing on the package.json:

  • the newer is not allowed, in the message OUTDATED is showed
  • the newer is allowed, in the message CANUPDATE is showed

In both cases the newer version discovered is showed.

Let me know if I made any kind of mistake here, such as this is not what was expected or if there are bugs I've not spotted.


lazywithclass added some commits Oct 10, 2011

Added support for issue #1428. Versions upper limit specified in pack…
…ages.json is ignored when launching a npm outdated [package], so if a newer version is found then the user is notified with a proper message formatted like this: "mkdirp@0.0.1 ./node_modules/mkdirp current=OUTDATED(0.0.7 available)". I still have to check if everything is ok for pull request (testing, corner cases, is this what was requested, ...)
Cleaned up the code so there is no need of specifying a callback when…
… invoking npm.commands.view; added a call to runNpmView when dealing with error while reading the filesystem

This feature looks great.

aseemk commented May 11, 2012



ghost commented Jul 1, 2012

So I created a tool to do just that: http://search.npmjs.org/#/npmedge

ARAtlas commented Oct 9, 2012


Ping, is there a reason why this is not moving?


domenic commented Sep 22, 2013

Fixed by 2f7fd62!

@domenic domenic closed this Sep 22, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment