-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Semver valid range considered out-of-date #80
Comments
Could you post the example module? |
@alanshaw I could, but you won't have access, since it's part of npmjs.org's new private modules offering. package.json looks like this:
I get the normal table output from david, claiming that "1.0.5" is the latest. We do have a tagged version: "1.0.5-cdn1" - could that be causing issues? |
Can you post the output from |
Sure thing:
|
Any chance you can give me read access to this module temporarily so I can debug? Also, are you using david programmatically, or on the command line? Either way, what options are you passing and what's the output? |
We're using it programmatically with |
I could probably mock it out but it would be way less work to just get temporary access - let me know what they say. |
@alanshaw I got the go-ahead to add you to one of our modules, vendor.backbone. This module is exhibiting the same issue: david isn't seeing
|
We use a few ranges such like
1.x.x
in a few situations very explicitly, though it's not common. When the module in question has a latest version of1.0.5
, david erroneously thinks that this is an out of date dependency.The text was updated successfully, but these errors were encountered: