Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

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

Closed
ryandesign opened this Issue · 20 comments
@ryandesign

I originally asked about this on the discussion group and was told to file an issue:

http://groups.google.com/group/npm-/browse_thread/thread/8030a3a14767f906

Suppose I want to restrict the version of a dependency in my package.json, because newer versions might not be compatible with my code:

{ 
        ... 
        "dependencies" { 
                ... 
                "mongoose": ">= 1.8.3 < 1.9" 
                ... 
        } 
        ... 
} 

"npm outdated" and "npm update" won't tell me about the existence of versions of mongoose newer than 1.8.x, but eventually such a version will be released (in fact mongoose 2 is already out), and I will want to know about that, so that I can update my code to use that newer version. Possibly "npm outdated" and "npm update" could say "Hey, 2.1.3 is available, but I'm only gonna give you 1.8.4 cause that's what you asked for." Or there could be a new npm command to check for this.

@lazywithclass lazywithclass referenced this issue from a commit
@lazywithclass lazywithclass 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, ...)
5bc6a62
@lazywithclass

Submitted a pull request #1638

@matthewmueller

+1 This is really useful for updating your module to use all the latest dependencies. I've had to npm view each of my modules to see what the latest is.

@aseemk

+1

@ghost

+1

@ghost

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

@Zearin

+1

@ARAtlas

+1

@enyo

I would love this feature as well. +1

@balupton

+1, npmedge works great but would be great if this happened out of the box with npm outdated

@75lb

+1 want

@cqql

+1

@gimenete

+1

@darsain

+1, this has been opened for 2 years already? :eyes:

@75lb
@robertkowalski robertkowalski referenced this issue from a commit in robertkowalski/npm
@robertkowalski robertkowalski Discover new versions with outdated
Add versions that are not matching the version specified in the
package.json as 'latest'.
Show versions that are specified by the package.json as 'wanted'

Fixes #1428
241b1fe
@robertkowalski robertkowalski referenced this issue from a commit in robertkowalski/npm
@robertkowalski robertkowalski Discover new versions with outdated
Add versions that are not matching the version specified in the
package.json as 'latest'.
Show versions that are specified by the package.json as 'wanted'

Fixes #1428
e337949
@robertkowalski robertkowalski referenced this issue from a commit in robertkowalski/npm
@robertkowalski robertkowalski Discover new versions with outdated
Add versions that are not matching the version specified in the
package.json as 'latest', at cost of one request more per package.

Show versions that are specified by the package.json as 'wanted'

Fixes #1428
76f7bdf
@kinergy

+1 This ticket has been open for quite some time - any chance of resolving it in favor of adding the requested functionality?

@tjunnone

I got tired of waiting, and created npm-check-updates. It will discover new package dependencies, and can optionally upgrade your package.json while keeping your semantic versioning restrictions (e.g. "1.2.x" becomes "1.3.x" when 1.3.0 is released).

@robertkowalski robertkowalski closed this issue from a commit
@robertkowalski robertkowalski Discover new versions with outdated
Add versions that are not matching the version specified in the
package.json as 'latest', at cost of one request more per package.

Show versions that are specified by the package.json as 'wanted'

Fixes #1428
2f7fd62
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.