-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to add names to different node versions #478
Comments
I'd also like to see something like the |
I too would like to see support for aliasing different versions similar to |
|
Aliases are on the roadmap. |
Again, aliases are on the roadmap for rt. See #565. |
We can use the alias to switch to a version or uninstal it. This feature was mentioned in the issues coreybutler#884, coreybutler#478, coreybutler#466 and coreybutler#461
If this is a question about how to use NVM4W, please use stackoverflow instead.
If this is an issue regarding antivirus, make sure you search the existing issues first.
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:
I have already...
My issue is related to (check only those which apply):
Expected Behavior
It would be a great feature to let the users name their node versions.
It wouldn't require changing any existing behaviour, it would be just 2 extra commands maybe:
So you don't have to remember which version are you using in which project.
I think it's a minimal effort change which brings a really good feature on the table.
The text was updated successfully, but these errors were encountered: