-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Can't resolve npm dependencies with a 0.0.0 version and pre-release #24550
Comments
The author of that package was just begging to uncover bugs with that versioning strategy. It seems like the node semver calculator doesn't even discover the versions of their package. The reason this doesn't work is because |
Thanks, @dsherret. Does Node and npm use a semantic versioning (semver) calculator that places versions above |
No, it's
We have the same behaviour, but we just have a small bug where we assume I was referring to this bug on the semver calculator website (https://semver.npmjs.com/): |
Description
When attempting to import the
postgraphile
package in Deno 1.44, an error is encountered indicating that the 'tamedevil' package cannot be found, even though it exists on npm. The issue appears to be related to the fact that one of its dependencies is a0.0.0
version.Steps to Reproduce
postgraphile@^5.0.0-beta.26
using the following code:Expected Behavior
The
postgraphile
package should import successfully without errors related to missing dependencies that exist on npm.Actual Behavior
The import fails with an error indicating that the 'tamedevil' package cannot be found, despite it being available on npm:
Additional Information
tamedevil
package on npm: tamedevil0.0.0
version, which might be causing the resolution problem.Suggested Fixes
Ensure that the npm package resolution in Deno correctly identifies and retrieves all dependencies, including pre-release versions and versions starting from
0.0.0
, from npm.Thank you for your assistance!
The text was updated successfully, but these errors were encountered: