-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Missing github-url-from-git
from npm@3 in Node v5 RC1
#3540
Comments
So it doesn't exist? I.e not checked in? Can you check if it's in the source?
|
in core
same as #3494 I suppose |
Is that even a dependency still? |
strange, RC1 works fine for me on OS X |
Is it possible to install it with nvm ? cc @ljharb |
@targos sadly I haven't yet had time to finish implementing it. Follow progress at nvm-sh/nvm#779 |
That module isn't used by npm@3 at all (it was supplanted by the more general
I'd love to know what module your |
(#3494 is caused by node's |
I am unable to reproduce on windows with a basic setup, and it also seems to work fine for @evanlucas. @rvagg I think this is on your end. |
I am also unable to reproduce on OSX |
|
Maybe related to #3606 |
I still get this with npm 5.0.0 (not rc) on Windows. Might be some installation issue with the upgrade. I also have moved my npm folder to /dev/npm instead of {APPDATA}/npm and updated npmrc. |
Hi, Just install Node.js v5.0.0 with npm 3.3.6 on Windows over an existing v0.12.x and I had the same issue. It seems that some old dependencies remain on the machine (the old folder nodejs/npm isn't removed) on installation. Removing everything fixed the problem for me. Thanks |
Same for me @chrilith.
Problem gone. |
A colleague on OS X installed the Node.js 4.2.2 LTS, then installed/upgraded to the Node.js 5.1.0 stable (using the .pkg files from the official website). We ended up with the issue reported here, and had to manually uninstall Node.js and reinstall 5.1.0 in order to fix things. Just FYI. |
Same problem here...Had to delete node_modules in usr/local/lib/ to fix things |
Again, same issue for me on OS X. But oddly I did not experience this issue on Windows 7. |
Had a same troubles on Windows 7 x64 npm info using [email protected] Download zip and install to And npm go to work, may be it will useful for somebody |
Thank you @surger. Worked for us. |
@chrilith thanks for your comment, just hit this issue and indeed it was residual files under the "Program Files/nodejs" directory causing the issue. |
@GregWoods That worked, thanks. |
How can I resolve the same problem ??? |
@Jameskmonger How did you resolve ? |
Uninstall |
This issue still exists when upgrading from Node v4 LTS to Node v5.9.1. |
@feross I think we should be potentially wiping |
@thealphanerd I agree, if you wipe the bundled npm from the previous version before installing there won't be problems. |
Doing what @rvagg stated resolved it for me without any issues. |
Currently using 5.0.0 installed via NVM on OSX, I tried deleting node_modules and the one in /usr/lib and reinstalling node, nothing appears to work..
Any ideas? Maybe i've done this the wrong way or i'm missing something obvious. |
Just installed Node 6.2.0 current on Mac OS X:
Will try to ** Update ** Running |
Thank you @stevenbeeckman
works |
@GregWoods thanks the below worked for me.. |
For me |
See npm/npm#14026 which is the same as this. IMO this bug should be reopened as this is really a Node installer issue, surely (it should remove any existing files before writing new ones). |
This is still an issue with v6.11.1 on Mac OSX. I get the "Cannot find module 'github-url-from-git'" error when attempting to do anything with NPM. I removed /usr/local/lib/npm and ran the installer again, which fixed it. I second re-opening this issue. I was able to solve it quickly (with the help of people here) but there's clearly an issue with the installer. |
If you have this issue, please run
sudo rm -rf /usr/local/lib/node_modules/
and try installing again. ~Fishrock123Just released v5.0.0 RC 1 and npm is borked:
/cc @iarna @Fishrock123
The text was updated successfully, but these errors were encountered: