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

Suggestion: wildcard major version to latest X.y..z #214

tomByrer opened this Issue Oct 24, 2016 · 4 comments


5 participants
Copy link

tomByrer commented Oct 24, 2016

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 10

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.
  • searched the issues (open and closed) to make sure this isn't a duplicate.

Expected Behavior

nvm install 6 uses the latest 6.. version, in this case v6.9.1
Typical behavior of nvm Bash script

Actual Behavior

nvm installed 6.0.0 (assumed null = 0)

Would be handy to when having to install the latest versions in a specific major version without having to visit the NodeJS website. Changing this behavior does have a slight potential of confusing current users, but is currently confusing of Mac devs using this on Windows. I'd say the added benefit latest security updates & bug fixes trumps.
Same suggestion goes for nvm use, etc.

If 'no, won't add', I'd like to document the current behavior.


This comment has been minimized.

Copy link

coreybutler commented Oct 26, 2016

This has been requested before and I do think it makes sense to have the absolute latest version downloaded/used. I'm still pretty pressed for time at the moment, but consider this on my to-do list..... I would gladly accept a PR if someone wants this before I get around to it.


This comment has been minimized.

Copy link

kylewuolle commented Nov 6, 2016

I submitted a PR for this #222


This comment has been minimized.

Copy link

navossoc commented Apr 8, 2017

@kylewuolle That is great, but I think you should go further and implement the same behavior on semver.

nvm install 6 = 6.10.2
nvm install 6.9 = 6.9.5
nvm install 6.9.2 = 6.9.2

For reference:

@coreybutler If someone sent a PR with that changes, are you going to support it?

@coreybutler coreybutler modified the milestone: 2.0.0 Jul 15, 2017

@coreybutler coreybutler added this to Planned in 2.0.0 Jul 15, 2017

@coreybutler coreybutler moved this from Planned to Backlog in 2.0.0 Jul 15, 2017


This comment has been minimized.

Copy link

Sieabah commented Oct 13, 2017

I've made a PR finishing the steps so install and use both have sane versions. #311


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