Isn't there a simple fix for the elevation required issue? #862
-
|
I know there's been lots of discussion around this before. Still, it looks to me like the root cause of current problems with NVM needing elevated permissions is the current definition of the NVM_SYMLINK environment variable pointing into the shared ProgramFiles folder and not into a per-user folder. I have modified that (and the corresponding PATH section), and I've been happy with the result for months. Here's a PowerShell script that does it (only for the current shell session): $nvmhome = $env:NVM_HOME # C:\Users\burt_\AppData\Roaming\nvm
$old = $env:NVM_SYMLINK # C:\Program Files\nodejs
$new = $nvmhome.Replace('nvm','nodejs')
$env:NVM_SYMLINK = $new # C:\Users\burt_\AppData\Roaming\nodejs
$env:Path = $env:Path.Replace($old, $new) # not required, just in caseIs there a reason the current installer wouldn't work with this simple change? I don't understand the InnoSetup stuff, or I would submit a PR. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
The installer already provides the option to specify whatever directory you want. I usually just install to That said, your script seems like a good option for those who have "directory selection remorse" and want to make a change. For most users, not having |
Beta Was this translation helpful? Give feedback.
-
|
Just a reminder, the winget installer isn't part of this project. It might be worth bringing this up with the folks maintaining that installer. |
Beta Was this translation helpful? Give feedback.
-
|
Oh! Interesting Corey! It looks like my thanks are due to @awdr74100 and @ItzLevvie for integrating NVM-Windows and Winget. Perhaps they can add some detail here. For anyone interested in looking, here is the manifest file. Technically the manifest isn't an installer, the current version references |
Beta Was this translation helpful? Give feedback.
-
|
The other change that could help is to use an NTFS junction rather than a symbolic link. I think this was discussed in #79. The windows architects implemented junction points as a more secure-by-default alternative. Comparison here. There are specific scenarios one can invent that might need the flexibility of a full symbolic link. Still, I think use cases involving nonprivileged single-user installation would not need symlinks. |
Beta Was this translation helpful? Give feedback.
-
|
💡 How about ensuring %NVM_SYMLINK% is a child of %NVM_HOME% ?
|
Beta Was this translation helpful? Give feedback.
-
|
@coreybutler, @awdr74100: there is a draft PR #865 with an update that eliminates the need for elevated execution for installation or use. This version currently does NOT support ALLUSERS installation or installation over an existing NodeJS install. I haven't ripped that code out; I don't have the options enabled. I started to test those scenarios but would like to discuss the desired behavior. |
Beta Was this translation helpful? Give feedback.
The installer already provides the option to specify whatever directory you want. I usually just install to
C:\nvm4w.That said, your script seems like a good option for those who have "directory selection remorse" and want to make a change.
For most users, not having
NVM_SYMLINKpointed to a protected directory would be enough. However; in some environments, symlinks themselves require elevated admin privileges, regardless of whether the directory is protected or not. This is prominent in older versions of Windows. Newer versions of Windows have "Developer Mode", which will help bypass elevation for symlinks on non-protected directories.