sermver calc with nvm 1.1.9

[ShiJuuRoku]

Issue:

With nvm 1.1.9
I think there is a problem with the calculation of the semver when it is not complete

How To Reproduce:

node> nvm install 14
  No Major.Minor.Patch elements found

node> nvm install 14.18.2
node> nvm use 14
  node vv14.18.2 (64bit) is not installed or cannot be found.
  

Expected Behavior:

node> nvm install 14
Should install the latest node 14 (v14.18.2)

node> nvm use 14
Should use v14.18.2
Log display vv14.18.2, there are two 'v'

[coreybutler]

This should be auto-expanding the version. I've marked this as a bug.

[coreybutler]

This has been re-released in v1.1.9 with a note in the change log referencing this issue. https://github.com/coreybutler/nvm-windows/releases/tag/1.1.9

[ShiJuuRoku]

The issue still exists for the command 'nvm use'

[coreybutler]

Technically the vv is a different issue (from No Major.Minor.Patch elements found), which has been filed as #703.

[chenxinyanc]

Technically the vv is a different issue (from No Major.Minor.Patch elements found), which has been filed as #703.

I bump into similar issue on nvm v1.1.9.

I've tried to open #703 but GitHub says the page does not exist. Is there anything I can do locally for this? Version abbreviation is a very handy feature...

[VsevolodChumachenko]

I downloaded the latest version and still have this problem

[karleinarb]

I am having the same issue as @VsevolodChumachenko
Downloaded the latest version today

[VsevolodChumachenko]

I am having the same issue as @VsevolodChumachenko Downloaded the latest version today

@karleinarb, I tried to install 1.1.7 version and it works for me

[Tanimpathan]

nvm use (select exact version downloaded like 14.19.0) did work for me

[steffy2110]

@coreybutler what do you suggest I have been following on this #706 issue that says access denied issues, I tried several times using nvm version 1.1.9

nvm use x.x.x command doesn't work in case of executing from VS code terminal when using 1.1.9 v of nvm,
it works on the admin terminal but I want to access it from vs code integrated terminal, and I don't want to change my system's setting to developer enable, is there any way that I can use node on nvm 1.1.9 on vs code?
I have tried downgrading node versions installation but still, access is denied, the tag of latest suggests that this issue was for version before Dec 15, 2021, I think it still isn't solved, correct me if I'm wrong, any advice you have on this, do share, thnx in advance!

[CraigMason]

I installed this from fresh today and have the issue described above. No previous versions of nvm-windows were on my system.

PS C:\Users\camason> nvm list

  * 10.16.2 (Currently using 64-bit executable)
PS C:\Users\camason> nvm install 16
Downloading node.js version 16.16.0 (64-bit)...
Extracting...
Complete


Installation complete. If you want to use this version, type

nvm use 16.16.0
PS C:\Users\camason> nvm use 16
node vv16.16.0 (64-bit) is not installed or cannot be found.
PS C:\Users\camason> nvm use 16.16.0
Now using node v16.16.0 (64-bit)
PS C:\Users\camason> nvm list

  * 16.16.0 (Currently using 64-bit executable)
    10.16.2

[coreybutler]

Windows requires permissions to create symlinks if you don't have admin rights. See Symlinks in Windows 10.

If you still don't have access, you have to assure you're not accessing a Windows protected directory (like C:\Program Files).

Finally, if you're on Windows 11, you may have to allow NVM4W in Windows Security.

For those using VS Code, Windows still requires the same permissions of the user that launched VS Code. The sledgehammer solution is to open VS Code as an admin. The more appropriate approach would be to grant your user account permissions to create symlinks and to assure the user account has access to modify the directory where the node root is defined. For an old but still relevant example, see Permission to make symbolic links in Windows 7.