Skip to content
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.

Unsupported protocol null for file paths #61

Open
moll opened this issue Jan 29, 2015 · 3 comments
Open

Unsupported protocol null for file paths #61

moll opened this issue Jan 29, 2015 · 3 comments

Comments

@moll
Copy link

moll commented Jan 29, 2015

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 with unsupported protocol null.

Cheers

@Raynos
Copy link
Contributor

Raynos commented Jan 29, 2015

@moll Interesting. I have never tried installing from tarballs before.

A contribution to support tarballs is welcome :)

@moll
Copy link
Author

moll commented Jan 29, 2015

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

@suprememoocow
Copy link

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)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants