You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
I just installed Node using the .msi for Windows 7 64-bit. It seemed to add npm to my PATH but not node. I was able to add it easily, but didn't see this detail in the instructions. A new developer may not know this is something they have to do if the install fails to do it. Adding a note to the installation instructions may be helpful.
Same here. Just installed using MSI installer, 64bit version. Path was incorrectly set. Even now, when I fixed it manually by adding "C:\Program Files\nodejs" (to user environment and system environment) and removing the Appdata one that points to an empty folder, I can only run it from any command-line if cmd.exe is run as Administrator. As a user, I can only run it from inside that folder.
I'm also facing the same problem. When I wrote echo $PATH in node.js terminal, It didn't show anything. I need to set the PATH to "C:\Program Files\nodejs". So, what should I do now?
I had the same issue, but I noticed if I opened up my environment variables, node was in my path already. Closing environment variables, re-opening my command windows and node is now on my path and available.
Yep, windows is like that, having to close out of the windows cmd line and
reopen is one of the reasons we like bash.
On Mar 9, 2014 7:30 AM, "rbellio" notifications@github.com wrote:
I had the same issue, but I noticed if I opened up my environment
variables, node was in my path already. Closing environment variables,
re-opening my command windows and node is now on my path and available.
Reply to this email directly or view it on GitHubhttps://github.com//issues/4356#issuecomment-37125852
.
You may misunderstand me. It wasn't the opening and closing of windows cmd line that fixed the issue for me. It was opening Environment Variables and closing it that made it work. It's almost as if Environment Variables did not recognize the change.
System wide variable changes are usually not fully recognized on windows
till after a reboot. ReOpening the cmd line has been required for years.
Power shell or Win8 may be better.
On Mar 9, 2014 9:02 AM, "rbellio" notifications@github.com wrote:
You may misunderstand me. It wasn't the opening and closing of windows cmd
line that fixed the issue for me. It was opening Environment Variables and
closing it that made it work. It's almost as if Environment Variables did
not recognize the change.
Reply to this email directly or view it on GitHubhttps://github.com//issues/4356#issuecomment-37127559
.
Yes, needing a reboot is something required, but other times simply opening a new Command Prompt windows is sufficient. Perhaps the installer should simply recommend a reboot after install to clear up the confusion when users try to instantly start using node.js from the command line?
This issue was moved to milestone 0.12.6 by mistake because it hadn't been closed after the fix landed and shipped with node v0.12.5. Moving it back to the 0.12.5 milestone to avoid confusion.
Activity
isaacs commentedon Dec 3, 2012
It should add them both. What was the
PATHvalue after running the installer/cc @piscisaureus @sblom
benirose commentedon Dec 3, 2012
I had just "C:\Users\brosenbach\AppData\Roaming\npm" as my PATH. I had to add ";C:\Program Files\nodejs" myself. Not sure why that was.
paulxtiseo commentedon Dec 6, 2012
Same here. Just installed using MSI installer, 64bit version. Path was incorrectly set. Even now, when I fixed it manually by adding "C:\Program Files\nodejs" (to user environment and system environment) and removing the Appdata one that points to an empty folder, I can only run it from any command-line if cmd.exe is run as Administrator. As a user, I can only run it from inside that folder.
MllePandaRoux commentedon Jul 4, 2013
Same issue here! :)
7oque commentedon Sep 2, 2013
This just happened to me with the installer: v0.10.17
(added roaming path and not path to application, in my case R:\Applications\nodejs)
jgillich commentedon Jan 3, 2014
Just had the same problem as @benirose on a fresh Windows 8.1 Pro installation.
TahsinAbrar commentedon Jan 10, 2014
I'm also facing the same problem. When I wrote echo $PATH in node.js terminal, It didn't show anything. I need to set the PATH to "C:\Program Files\nodejs". So, what should I do now?
marceloco commentedon Feb 25, 2014
I just had the same problem on a Surface Pro running Windows 8.1 Pro (64 bit).
rbellio commentedon Mar 9, 2014
I had the same issue, but I noticed if I opened up my environment variables, node was in my path already. Closing environment variables, re-opening my command windows and node is now on my path and available.
rjt commentedon Mar 9, 2014
Yep, windows is like that, having to close out of the windows cmd line and
reopen is one of the reasons we like bash.
On Mar 9, 2014 7:30 AM, "rbellio" notifications@github.com wrote:
rbellio commentedon Mar 9, 2014
You may misunderstand me. It wasn't the opening and closing of windows cmd line that fixed the issue for me. It was opening Environment Variables and closing it that made it work. It's almost as if Environment Variables did not recognize the change.
rjt commentedon Mar 9, 2014
System wide variable changes are usually not fully recognized on windows
till after a reboot. ReOpening the cmd line has been required for years.
Power shell or Win8 may be better.
On Mar 9, 2014 9:02 AM, "rbellio" notifications@github.com wrote:
dougwilson commentedon Mar 9, 2014
Yes, needing a reboot is something required, but other times simply opening a new Command Prompt windows is sufficient. Perhaps the installer should simply recommend a reboot after install to clear up the confusion when users try to instantly start using node.js from the command line?
dougwilson commentedon Mar 9, 2014
Actually, I take that back. The installer should be able to get the new PATH picked up by broadcasting a
WM_SETTINGCHANGEmessage to all the open windows. More information at https://stackoverflow.com/questions/3636055/how-to-modify-the-path-variable-definitely-through-the-command-line-in-windowsIt seems from these reports that this isn't being done, so if the installer did this, it should fix the issue.
dougwilson commentedon Mar 9, 2014
For those so inclined to make a PR to this, it looks like someone has posted instructions for how to accomplish this in WiX: http://www.kajabity.com/2013/09/an-update-to-the-apache-maven-installers-broadcasting-wm_settingchange-to-update-environment-variables/
35 remaining items
orangemocha commentedon Jun 23, 2015
Fixed with f50c37d and shipped in v0.12.5.
misterdjules commentedon Jun 24, 2015
This issue was moved to milestone 0.12.6 by mistake because it hadn't been closed after the fix landed and shipped with node v0.12.5. Moving it back to the 0.12.5 milestone to avoid confusion.
ArtemKolodko commentedon Jun 23, 2016
@uniring it works from console, thank you
win,msi: Added empty InstallExecuteSequence group
win,msi: broadcast WM_SETTINGCHANGE after install