Skip to content
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

Still gets a problem with github-url-from-git module not found on Windows #3786

Closed
jbergens opened this issue Nov 12, 2015 · 7 comments
Closed
Labels
npm Issues and PRs related to the npm client dependency or the npm registry.

Comments

@jbergens
Copy link

This means I cannot even run "npm install" for this project.I attach a log from npm. Not sure if this i npm or node but there was a similar issue for a release candidate.
npm-debug_v3_3_6.log.txt

@mscdex mscdex added the npm Issues and PRs related to the npm client dependency or the npm registry. label Nov 12, 2015
@Fishrock123
Copy link
Contributor

Probably related to #3606

I don't know where global modules are stored on windows, but you'll want to find and delete that, then re-install node.

i.e. on Unix it is /usr/local/lib/node_modules/npm.

@targos
Copy link
Member

targos commented Nov 12, 2015

i.e. on Unix it is /usr/local/lib/node_modules/npm.

I'm not sure about that. They were installed here before, but now on our servers (CentOS) they end up in /path/to/node/lib/node_modules. It seems to have changed with npm 3 (to be confirmed).

@Fishrock123
Copy link
Contributor

Oh. Well wherever they previously were is what's causing issues.

@cjihrig
Copy link
Contributor

cjihrig commented Nov 12, 2015

Closing, as I don't think there is anything actionable that we can do here. This seems to be more related to npm.

@cjihrig cjihrig closed this as completed Nov 12, 2015
@cjihrig
Copy link
Contributor

cjihrig commented Nov 12, 2015

Actually, reopening, as the other issue seems to imply it's related to the installer.

@Trott
Copy link
Member

Trott commented Jun 6, 2016

Does it make sense to close this in favor of #3606? If it's because of the installer, then that's probably the right issue?

@joaocgreis
Copy link
Member

I cannot reproduce this, the module exists and installs fine.

@jbergens if you're still having this issue, can you run RD /S /Q %APPDATA%\npm-cache and try again? I'll close this for now, but we can reopen if this is still a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry.
Projects
None yet
Development

No branches or pull requests

7 participants