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

how-to-npm on windows #31

Closed
Quas94 opened this issue Jul 8, 2015 · 9 comments
Closed

how-to-npm on windows #31

Quas94 opened this issue Jul 8, 2015 · 9 comments

Comments

@Quas94
Copy link

Quas94 commented Jul 8, 2015

Can't get past the very first step (verifying npm is up-to-date).

C:\Users\Quasar\Desktop\how-to-npm>how-to-npm verify
verifying that npm is installed...
Uh oh!  npm had a problem! {"killed":false,"code":1,"signal":null,"cmd":"C:\\Win
dows\\system32\\cmd.exe /s /c \"C:\\Program Files\\nodejs\\npm.CMD --version\""}

'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
#########################################
###   YOUR SOLUTION IS NOT CORRECT!   ###
#########################################

Looks like something to do with the space in the Program Files folder.
Anything I can do about this other than re-installing Node itself to a different folder that doesn't have space characters?

@Quas94
Copy link
Author

Quas94 commented Jul 9, 2015

I just completed all the steps whilst skipping verification for the parts which produced this error. Just a heads up that this issue exists, though.

@No9
Copy link

No9 commented Jul 15, 2015

There are 3 patches that attempt to to solve this

#17
#19
#32

And this was the original bug report
#11

@isaacs @mmalecki @linclark
Please can we get this in somehow?

@kaiyoma
Copy link

kaiyoma commented Dec 7, 2015

Seeing this as well. Quotes around the file location of the npm executable are necessary on Windows because the default install location for Node.js has spaces in its name.

@kaiyoma
Copy link

kaiyoma commented Dec 7, 2015

The problem seems to be worse now than when the OP submitted the issue. I can't advance past step 2 (Login) because attempting to skip verification also results in an error:

...\Kyle\Portfolio\Studying\temp-workspace> how-to-npm verify
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

Uh oh!
It looks like something went wrong
#########################################
###   YOUR SOLUTION IS NOT CORRECT!   ###
#########################################



...\Kyle\Portfolio\Studying\temp-workspace> how-to-npm verify skip
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

Uh oh!
It looks like something went wrong
#########################################
###   YOUR SOLUTION IS NOT CORRECT!   ###
#########################################

@8fdafs2
Copy link

8fdafs2 commented Aug 27, 2016

try run how-to-npm in 'Node.js command prompt' see if it solves the problem

@cltsao
Copy link

cltsao commented Sep 13, 2016

@8fdafs2 Thanks. Running how-to-npm in Node.js command prompt solved the problem in my Windows environment.

@itzsaga
Copy link
Member

itzsaga commented Dec 23, 2016

Just updating with my error. This is still an issue and needs more instruction for people to work around.

λ how-to-npm verify
verifying that npm is installed...
Uh oh!  npm had a problem! {"killed":false,"code":1,"signal":null,"cmd":"C:\\Program Files\\nodejs\\npm.CMD --version"}
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
#########################################
###   YOUR SOLUTION IS NOT CORRECT!   ###
#########################################

@itzsaga
Copy link
Member

itzsaga commented Dec 24, 2016

Possible solution:
Instruct people on Windows to run npm -v and if the version is high enough instruct people to run how-to-npm verify skip. Otherwise upgrade npm via npm install npm.
I believe this could solve this issue but I'm not 100% on this idea.

@watilde
Copy link
Member

watilde commented Feb 18, 2017

#108 is shipeed as v2.4.1. Closing as resolved :)

@watilde watilde closed this as completed Feb 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants