-
Notifications
You must be signed in to change notification settings - Fork 220
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
Comments
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. |
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. |
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:
|
try run how-to-npm in 'Node.js command prompt' see if it solves the problem |
@8fdafs2 Thanks. Running how-to-npm in Node.js command prompt solved the problem in my Windows environment. |
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! ###
######################################### |
Possible solution: |
#108 is shipeed as v2.4.1. Closing as resolved :) |
Can't get past the very first step (verifying npm is up-to-date).
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?
The text was updated successfully, but these errors were encountered: