nvm-windows: "$ nvm install 5" does unexpected thing

My Environment

  • Windows 7 or below (not truly supported due to EOL)
  • 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 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
  • 32 or 64 bit support

Expected Behavior

nvm install 5

would install latest version (whatever it was)

Actual Behavior


C:\Users\denman\WebstormProjects\suman>nvm install 5
panic: runtime error: index out of range

goroutine 1 [running]: /C/Users/Corey/Documents/workspace/nvm-windows/src/nvm/web.IsNode64bitAvailable(0x12226134, 0x1, 0x674700) C:/Users/Corey/Documents/workspace/nvm-windows/src/nvm/web/web.go:153 +0x157 main.install(0x12226134, 0x1, 0x674700, 0x2) C:/Users/Corey/Documents/workspace/nvm-windows/src/nvm.go:171 +0x484 main.main() C:/Users/Corey/Documents/workspace/nvm-windows/src/nvm.go:65 +0x64e

Steps to reproduce the problem:

just run

$ nvm install 5

thanks, this is working for me so far! just wanted to let you know that I expected that command to work. Cheers!

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 17
  • Comments: 18 (5 by maintainers)

Commits related to this issue

Most upvoted comments

Some other aliases would also be useful, like unix nvm or node’s oficial docker image

nvm install lts -> installs latests lts version nvm install boron -> installs latest boron version And as stated before nvm install 6 -> installs ^6.x.x semver style

This is actually more important than facilitating convenience. It is needed on CI servers to ensure the latest version is installed. Otherwise I must update our CI configuration every time Node releases a patch.

Any updates on this? It has been 5 years and I just started using NVM and I came to check why would I get Node 14.0.0 instead of latest if i specify only the Major?

@insin - Yeah, nvm use should pretty much always mirror nvm install syntax. When I get around to implementing this, it should be in both.

Ok, I see there are also two issues for mvn use

Hmm, I’m wondering is that the same code path? I think not, nvm use should consider only locally insntalled ones

Thanks for the feedback. While this isn’t a bug, I appreciate knowing this is the behavior you were expecting. I’ve marked it as an enhancement request.