Feature Request: Parallel Aliased installs

[JDillon522]

My Environment

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

• [ ] Windows 8

• [ ] Windows 8.1

• [X] 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:

• [X] 1.1.7
• [ ] 1.1.6
• [ ] 1.1.5
• [ ] 1.1.4
• [ ] 1.1.3
• [ ] 1.1.2
• [ ] 1.1.1
• [ ] Older
• [ ] OTHER (Please Specify)

I have already...

• [x] read the README to be aware of npm gotchas & antivirus issues.
• [x] reviewed the wiki to make sure my issue hasn't already been resolved.
• [x] verified I'm using an account with administrative privileges.
• [x] searched the issues (open and closed) to make sure this isn't a duplicate.
• [x] 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)
• [x] A feature request

Expected Behavior

I'd like the ability to have alias installs of node. My specific issue is a good illustration: I have two Angular projects I need to support, both with the same versions of node, but with different globally install Angular CLI versions. I'd like to set an alias install of node with a different set of globally installed modules based on specific needs.

Actual Behavior

Steps to reproduce the problem:

[coreybutler]

Interesting idea. I'll take it into consideration for a future version.

[tvkit]

Interesting idea. I'll take it into consideration for a future version.

An excellent idea that would help to solve the random tooling issues that pop up from time to time. Maybe something like:

nvm install 10.17 --alias gulp3

nvm use gulp3
  gulp3
  Now using gulp3, node v10.17.0 ( 64-bit)

nvm list
  * gulp3 (Currently using 10.17.0, 64-bit executable)
    13.1.0
    10.17.0

where the symlink would point to the alias:

dir
   11/11/2019  06:01 PM    <SYMLINKD>     nodejs [C:\Users\vdsuser\AppData\Roaming\nvm\gulp3]