You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.
I'm trying to see if npm-shrinkwrap fixes NPM's problems related to shrinkwrapping projects that have modules installed from either a tarball or an unpacked directory. Seems that it dies outright instead.
That is, with modules installed from ./vendor/foo.tgz or from ./modules/foo, npm-shrinkwrap dies with unsupported protocol null.
Cheers
The text was updated successfully, but these errors were encountered:
I found that upgrading NPM to at least v2.3.0 fixes another issue I was having that made me look into this project. Sorry, for now I'll remain using with the built-in shrinkwrapping. :-)
Feel free to do what you deem most useful with this issue report. ;-)
We're using local directories with the file: protocol. I've created #81 which fixes the problem for directories and should work for tarballs too (although I haven't actually tested that yet)
Hey,
I'm trying to see if
npm-shrinkwrap
fixes NPM's problems related to shrinkwrapping projects that have modules installed from either a tarball or an unpacked directory. Seems that it dies outright instead.That is, with modules installed from
./vendor/foo.tgz
or from./modules/foo
,npm-shrinkwrap
dies withunsupported protocol null
.Cheers
The text was updated successfully, but these errors were encountered: