This repository has been archived by the owner. It is now read-only.

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

Closed
ryandesign opened this Issue Sep 20, 2011 · 20 comments

Comments

Projects
None yet
@ryandesign

ryandesign commented Sep 20, 2011

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

This comment has been minimized.

Show comment
Hide comment
@lazywithclass

lazywithclass Nov 1, 2011

Submitted a pull request #1638

lazywithclass commented Nov 1, 2011

Submitted a pull request #1638

@matthewmueller

This comment has been minimized.

Show comment
Hide comment
@matthewmueller

matthewmueller Apr 9, 2012

+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.

matthewmueller commented Apr 9, 2012

+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.

@wachunga

This comment has been minimized.

Show comment
Hide comment
@wachunga

wachunga commented Apr 16, 2012

+1

3 similar comments
@exortech

This comment has been minimized.

Show comment
Hide comment
@exortech

exortech commented Apr 16, 2012

+1

@aseemk

This comment has been minimized.

Show comment
Hide comment
@aseemk

aseemk commented May 11, 2012

+1

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost commented Jul 1, 2012

+1

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jul 1, 2012

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

ghost commented Jul 1, 2012

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

@snostorm

This comment has been minimized.

Show comment
Hide comment
@snostorm

snostorm commented Jul 31, 2012

+1

3 similar comments
@mtkopone

This comment has been minimized.

Show comment
Hide comment
@mtkopone

mtkopone commented Aug 28, 2012

+1

@Zearin

This comment has been minimized.

Show comment
Hide comment
@Zearin

Zearin commented Sep 9, 2012

+1

@ARAtlas

This comment has been minimized.

Show comment
Hide comment
@ARAtlas

ARAtlas commented Oct 9, 2012

+1

@enyo

This comment has been minimized.

Show comment
Hide comment
@enyo

enyo Jan 9, 2013

I would love this feature as well. +1

enyo commented Jan 9, 2013

I would love this feature as well. +1

@jamesjwood

This comment has been minimized.

Show comment
Hide comment
@jamesjwood

jamesjwood commented Jan 24, 2013

+1

1 similar comment
@stephenhandley

This comment has been minimized.

Show comment
Hide comment
@stephenhandley

stephenhandley commented Feb 13, 2013

+1

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Feb 16, 2013

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

balupton commented Feb 16, 2013

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

@75lb

This comment has been minimized.

Show comment
Hide comment
@75lb

75lb Mar 14, 2013

+1 want

75lb commented Mar 14, 2013

+1 want

@cqql

This comment has been minimized.

Show comment
Hide comment
@cqql

cqql commented Mar 23, 2013

+1

1 similar comment
@gimenete

This comment has been minimized.

Show comment
Hide comment
@gimenete

gimenete commented May 8, 2013

+1

@darsain

This comment has been minimized.

Show comment
Hide comment
@darsain

darsain Jun 27, 2013

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

darsain commented Jun 27, 2013

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

@75lb

This comment has been minimized.

Show comment
Hide comment
@75lb

75lb Jun 27, 2013

i expect due to its 'unessential yet nice to have' status..

On 27 Jun 2013, at 13:12, Darsain notifications@github.com wrote:

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


Reply to this email directly or view it on GitHub.

75lb commented Jun 27, 2013

i expect due to its 'unessential yet nice to have' status..

On 27 Jun 2013, at 13:12, Darsain notifications@github.com wrote:

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


Reply to this email directly or view it on GitHub.

robertkowalski added a commit to robertkowalski/npm that referenced this issue Jul 6, 2013

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 npm#1428

robertkowalski added a commit to robertkowalski/npm that referenced this issue Jul 24, 2013

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 npm#1428

robertkowalski added a commit to robertkowalski/npm that referenced this issue Sep 5, 2013

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 npm#1428
@kinergy

This comment has been minimized.

Show comment
Hide comment
@kinergy

kinergy Sep 5, 2013

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

kinergy commented Sep 5, 2013

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

@tjunnone

This comment has been minimized.

Show comment
Hide comment
@tjunnone

tjunnone Sep 7, 2013

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).

tjunnone commented Sep 7, 2013

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).

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