Skip to content
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

Open
8 of 30 tasks
petrovicz opened this issue Oct 1, 2019 · 6 comments
Open
8 of 30 tasks

Ability to add names to different node versions #478

petrovicz opened this issue Oct 1, 2019 · 6 comments

Comments

@petrovicz
Copy link

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:

  • 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...

  • 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)
  • A feature request

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:

  • One is for assigning a custom name to a version
  • And another one for setting the version based on the custom name

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.

@petrovicz petrovicz changed the title Ability to add names to different npm versions Ability to add names to different node versions Oct 1, 2019
@rbuckton
Copy link
Contributor

I'd also like to see something like the nvm alias feature from nvm on Linux. I've "worked around" this by adding a directory symlink in the root for things like v{alias}.0.0.

@joesaraceno
Copy link

I too would like to see support for aliasing different versions similar to nvm on Linux. I would also like to see some default aliases come installed, that either reference LTS versions, default, latest, etc.

@johnnyoshika
Copy link

alias would be a nice addition.

@coreybutler
Copy link
Owner

Aliases are on the roadmap.

This was referenced Aug 27, 2020
@Vyoam
Copy link

Vyoam commented Aug 29, 2021

Would be nice to have this.

Some related links...

A PR which somehow was abandoned

#513

Duplicates...

#524
#543
#503
#558
https://github.com/coreybutler/nvm-windows/issues?q=alias

@coreybutler
Copy link
Owner

Again, aliases are on the roadmap for rt. See #565.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants