Feature request: setting a "default" version with the ability to change to the "default" version

[b-strauss]

We have nvm on a Windows Server system with several node versions installed. In our CI we need a special version for certain configurations, but only for a handful. Most (95%) of our configurations can use the same version. It would be great to have the possibility to set a "default" version in nvm, something like nvm set_default 10.16.0. And then on whatever version you are, after the build script with the special version is done you can change back to the "default" one with another command, e.g.: nvm use default. Currently we have to set the version in every build script, even if 95% of the time it's the same version.

[nishants]

or may be use the same command as in nvm nvm alias default 10.16.0

[csalmeida]

I am having the same issue, running nvm alias default 14.15.1:

Running version 1.1.7.

Usage:

  nvm arch                     : Show if node is running in 32 or 64 bit mode.
  nvm install <version> [arch] : The version can be a node.js version or "latest" for the latest stable version.
                                 Optionally specify whether to install the 32 or 64 bit version (defaults to system arch).
                                 Set [arch] to "all" to install 32 AND 64 bit versions.
                                 Add --insecure to the end of this command to bypass SSL validation of the remote download server.
  nvm list [available]         : List the node.js installations. Type "available" at the end to see what can be installed. Aliased as ls.
  nvm on                       : Enable node.js version management.
  nvm off                      : Disable node.js version management.
  nvm proxy [url]              : Set a proxy to use for downloads. Leave [url] blank to see the current proxy.
                                 Set [url] to "

[NoMercy235]

Is there any update on this? I am running into the same issue on Windows.

nvm alias default <version> is not recognized as a command, and nvm keeps loading the first version of Node that was installed whenever I restart my PC. If I run nvm use <version>, it keeps using it (even on new terminals) until the next restart.

[ariadne-github]

or may be use the same command as in nvm nvm alias default 10.16.0

This works only for Linux version of NVM...

[blasco]

Is there still no nvm alias default equivalent?

[i-zanis]

Hello,

I switched from WSL ZSH to PowerShell and I am currently facing the same problem. nvm alias default is not recognized.

[coreybutler]

NVM for Windows does not have custom aliases, which is why this is labeled as an enhancement request.

[Lunatunny]

I would also very much like this. I don't want to remember what version my project needs.

[hossam37x]

Is there still no way to set the default for windows?

[tiagofemavivo]

Also interested in this. No way to set default?

[sanzserif]

still rooting for this feature 😥

[Fantantonio]

Having this functionality built in would be very helpful!

[htutwaiphyoe]

I get this error too. Even though I changed node version with nvm with nvm alias default v20, I still need to change again after my laptop shutdown. Any possible solution?

[ShinobiWPS]

After many years of keeping an eye on it, I changed version manager for Windows (nvs, or volta)