Github Dependency Shorthand Not Working (Organization/Repository) #4732
Comments
Still broken in (changed name of organization/project)
|
I was having this error as well, I got it to work with this syntax:
|
@nickbuddendotcom thanks, I'll try that and upgrade my npm for now. The main issue is that the shorthand syntax is documented on npm.org as being valid. So if it's in the documentation it needs to work. Or we need to remove it from the documentation and then we can close the bug as well. I'm fixing some stuff in my codebase today but when I'm done I'm going to investigate this bug again on my end and see if the @npm team has fixed anything related to it. |
The shorthand syntax is valid, but it doesn't send authentication, as npm doesn't know it. Since this is a private repository, GitHub fails the clone. This isn't a bug with npm. |
@terinjokes thank you for this update. Why does it work prior to npm 1.4.0? What changed? |
Just as an FYI I was also able to work-around this issue by specifying the branch with the short-hand ... Tested on npm 1.4.3 |
|
Is this still an issue? We've tweaked a lot around caching git dependencies over the last few months, and I'd like to know if we missed something. |
This appears to be working for me. Just did:
on a private repo and it worked.
Thanks a bunch for that, guys! |
Great! Closing as resolved! |
No, it's still broken. We ran into it today with this combo:
Our package.json syntax was working previously. Now npm fails attempting to use git/ssh instead of https. |
Oh, looks like we have a different issue. Basic 'git clone' on my repo suddenly stopped working:
I haven't touched the repo for months. I hope there's not corruption on Github. |
@markstos Also, your version of npm is way old, despite being freshly installed. The latest is |
I can install private repositories with: Now it gets weird.. I've just realized I've had another (private) repository in the |
Anything after 1.4 is not allowing
Organization/Package
to be installed vianpm install
.My package.json:
Ok, installed straight from nodejs.org (on OSX 10.9)
node --version v0.10.26
npm --version 1.4.4
github.com/Organization/package does exist, but it's private. Is there a missing step somewhere to connect to private repos that got lost when I updated?
Rolled back to 1.3.24 and worked my way to find where in the upstream it breaks. Hopefully this helps.
sudo npm install npm@1.4.0 -g
BROKENsudo npm install npm@1.3.26 -g
works..sudo npm install npm@1.3.25 -g
workssudo npm install npm@1.3.24 -g
worksOriginal (closed) issue where this was discovered: #4725
The text was updated successfully, but these errors were encountered: