Nvm-windows: add support for --lts=releasename (and probably fix reporting unknown things)

Created on 20 Sep 2018 · 3Comments · Source: coreybutler/nvm-windows

In order to ensure code is tested correctly the nvm use --lts=releasename is fairly essential, but windows devs can't currently use that. Instead, they get the following error:

c:\Users\Me\Documents\git\test>nvm install --lts=Carbon
--lts=Carbon.0.0
Node.js v--lts=Carbon.0.0 is only available in 32-bit.

Which is wrong thrice (that's a runtime flag, not a version name, even though it's treating it as name, it's clearly not checking the list of available node versions to say "hey that's not a thing I know", and even though it doesn't know this thing, it claims to know it only has a 32 bit version available)

enhancement request help wanted

Source

Pomax

👍3

All 3 comments

First, --lts is not a supported flag (nvm help is fairly specific about this). The only runtime flag supported is --insecure.

Which version are you running? The message should be a little different if you're running 1.1.7.

Installing by release name could be possible since the data is available, but I won't have time to add this myself. I'd consider a PR.

coreybutler on 21 Sep 2018

That's my point. "the other nvm" offers --lts as an install flag because being able to tell nvm to install the latest LTS version makes life much, much easier for testing, because it lets you add node scripts like "test:lts" and have it run everything prefixed with an "nvm use --lts=carbon" to test against 8.xLTS "whatever that is right now".

Would you know someone else who could add this? (because I do not have the knowledge to add this for you)

Pomax on 21 Sep 2018

👍1

+1, and for support for nvm install lts/* / nvm use lts/*.