Feature request : Add a -use switch to the install command

[stevebeauge]

My Environment

• Windows 7 or below (not truly supported due to EOL - see wiki for details)

• Windows 8

• Windows 8.1

• Windows 10

• Windows 10 IoT Core

• Windows Server 2012

• Windows Server 2012 R2

• Windows Server 2016

• My Windows installation is non-English.

I'm using NVM4W version:

1.1.7

I have already...

• read the README to be aware of npm gotchas & antivirus issues.
• reviewed the wiki to make sure my issue hasn't already been resolved.
• verified I'm using an account with administrative privileges.
• searched the issues (open and closed) to make sure this isn't a duplicate.
• made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

• settings.txt
• proxy support (Have you tried version 1.1.0+?)
• 32 or 64 bit support (Have you tried version 1.1.3+?)
• Character escaping (Have you tried version 1.1.6+?)
• A standard shell environment (terminal/powershell)
• A non-standard shell environment (Cmder, Hyper, Cygwin, git)

Expected Behavior

It would be cool to add a -use switch to the install command, in order to allow one line install and use.

ex:

nvm install 13.2.0 -use

to be the equivalent of :

nvm install 13.2.0
nvm use 13.2.0

Or, maybe, an alternative could be to add a -install switch to the use command, to allow installing the new version if not yet installed.

nvm use 13.2.0 -install

Actual Behavior

Steps to reproduce the problem:

[coreybutler]

These concepts have been mentioned before, but I like the idea of both flags.

Some users have requested that nvm use x.x.x would auto-install if it doesn't already exist. Some have also requested that nvm install x.x.x would auto-"use". Ultimately, I think it would be best to let users specify a default (i.e. preferences) and use flags to override preferences when necessary.

I've marked this as an enhancement request. There's a reasonable chance this could make it into a near future release (as soon as I can get the release process automated.... that has taken quite awhile).