Closed kanongil closed 7 years ago
I definitely agree that they are allowed (based on the official format docs), but in my local package-lock.json
/ npm-shrinkwrap.json
tests all of the version
fields are semver compatible version numbers. Like:
"resolve": {
"version": "1.3.3",
"resolved": "https://registry.npmjs.org/resolve/-/resolve-1.3.3.tgz",
"integrity": "sha1-ZVkHw0aahoDcLeOidaj91paR8OU=",
"dev": true
}
I'm curious why version
has these URL's in your case...
I'm not sure about the exact trigger. I don't seem to be able to replicate it again.
However, others seems to be able to: https://github.com/npm/npm/issues/17187 & https://github.com/npm/npm/issues/16926.
When I run any
ember
command I get a long list of missing packages:Apparently, a bunch of the packages use the package download url as the
version
innpm-shrinkwrap.json
, eg.:As far as I can tell, it is allowed within the design of package locks, and needs to be handled here.
I suspect the solution would be to also do a check against the
"_resolved"
field in the installedpackage.json
?