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

Fixed Error 1909 and NPM works but I keep getting a weird error before NPM runs. #11749

Closed
andrew-vicencio opened this issue Mar 8, 2017 · 3 comments
Labels
npm Issues and PRs related to the npm client dependency or the npm registry. question Issues that look for answers.

Comments

@andrew-vicencio
Copy link

Version: 6.10.0 and NPM 4.3.0/3.10.10
Platform: 32-bit Windows

I was able to fix Error 1909 using the instructions in #8141. I created an npm folder in %APPDATA% and running npm install npm -g in command line while running as administrator. I also changed the environment variable from C:\Program Files (x86)\nodejs\ to C:\Program Files (x86)\nodejs.

So NPM is now installed in %APPDATA% and the enviro var is correct but I keep getting an error before NPM runs. You can see it in the first screen shot below. In the second screen shot, you can see that I can install the latest version (4.3.0) but when I run npm -v, it still says that it is version 3.10.10

I can't find anybody else with the same problem and I don't know what to do from here. Any help would be great, thank you.

Error:
'CALL "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" prefix -g' is not recognized as an internal or external command,
operable program or batch file.

2017-03-08

2017-03-08 1

@mscdex mscdex added the npm Issues and PRs related to the npm client dependency or the npm registry. label Mar 8, 2017
@ChALkeR ChALkeR added the question Issues that look for answers. label Mar 9, 2017
@watilde
Copy link
Member

watilde commented Mar 12, 2017

Hello! This issue seems same with the following issue reports:

Can you possibly make sure your environment variable called ComSpec as a single value?

@andrew-vicencio
Copy link
Author

@watilde It had one value but it also had a semi colon. I don't know if that would really change anything but thank you! There are no errors now.

@watilde
Copy link
Member

watilde commented Mar 18, 2017

@andrew-vicencio That's great! Happy to hear that.
As we see the similar issues, it's better to report it to npm repository for next time btw :)

Closing as resolved.

@watilde watilde closed this as completed Mar 18, 2017
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. question Issues that look for answers.
Projects
None yet
Development

No branches or pull requests

4 participants