You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
I have already...
Expected Behavior
nvm install 6
uses the latest 6.. version, in this case v6.9.1Typical 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.
The text was updated successfully, but these errors were encountered: