Install node.js 4.2.5 - most stable at the moment #1432
Conversation
Fix Android SDK installation Fix nativescript cli installation See #1429
| $oldPathUser = [Environment]::GetEnvironmentVariable("PATH", "User") | ||
| $pathMachine = [Environment]::GetEnvironmentVariable("PATH", "Machine") | ||
| $myPath = [Environment]::GetEnvironmentVariable("PATH") | ||
| [Environment]::SetEnvironmentVariable("PATH", "$myPath;$oldPathUser;$pathMachine;$env:ProgramFiles\nodejs") |
There was a problem hiding this comment.
I've not tested it, but according to this forum the PATH will not be "set" in the current Shell until you restart:
To set it PERMANENTLY you use SetEnvironmentVariable, but to have it
take effect NOW you need to use the Env: drive.
There was a problem hiding this comment.
According to MSDN the value will not be set until PowerShell is restarted:
Or at least it didn’t show up until we restarted PowerShell. (Or started up a new instance of PowerShell.)
Maybe we have to use full path to npm (from node installation).
source
There was a problem hiding this comment.
I am modifying the environment of the currently running PowerShell process, and not the User or System ones. So the forum post and the MSDN article are correct, but not applicable to the code. I can use the shorter syntax though, I did not know it.
We cannot use the full path to npm. This was my first approach and it failed - something (npm, dependencies, or our code) executes node without full path and the installation of the CLI fails because it cannot find node.exe.
There was a problem hiding this comment.
Ok, thanks for the explanation :)
|
👍 |
Install node.js 4.2.5 - most stable at the moment
Fix Android SDK installation
Fix nativescript cli installation
See #1429