02.03.2023: Full user mode

[Isotop7]

Is your feature request related to a problem? Please describe. When deploying nvm-windows centrally without having administrative permissions, every change of the node version triggers an elevation in permissions.

Describe the solution you'd like Complete user mode, where versions are download to appData folder and symlinked from there and user based env variables are used

Describe alternatives you've considered We're using AdminByRequest but every change needs a approval on our end

Additional context Here the call is already elevated. Wouldn't a normal mklink in a user based folder (%APPDATA%) work also?

Please use the reactions to cast a vote in favor of or against this feature suggestion »

[coreybutler]

This is actually how NVM4W was originally designed, but there were a number of complaints about it not being in Program Files. In v1.1.8, we worked around UAC prompts, and many users didn't approve because they wanted to be notified. Bottom line: we've flip-flopped on this issue several times and there's no pleasing everyone.

Technically, there are, of course, ways to simplify this experience based on how NVM4W needs to be used in any given environment. However; as the JS ecosystem has grown, it is clear there are quite a few of these use cases (solo devs, enterprise dev, CI/CD, etc) that all need special attention. I cannot support them all on my own. For this reason, this issue will be addressed in Runtime.

[chill389cc]

@Isotop7 it is fairly easy to change the default directories while running the nvm-windows installer so that it works in user-only mode. That is, as long as you have 'Developer Mode' enabled in the Windows Developer Settings. Edit: and you have to have admin rights to open the installer. But as long as you have developer mode enabled and you can get the installer open, you're home free.