"nvm list available" doesn't fails with error 404

[lashchev]

What happened?

Downloaded and used the latest NVM4W installer on the fresh Win11 machine today. In the admin console, nvm list available fails with the following error:

Error retrieving "https://nodejs.org/dist/latest-available/SHASUMS256.txt": HTTP Status 404 Such a page indeed doesn't exist.

nvm install works fine.

What did you expect to happen?

Expected a list of versions available to install

Version

1.1.11 or newer (Default)

Which version of Windows?

Windows 11+

Which locale?

None

Which shell are you running NVM4W in?

Command Prompt

User Permissions?

Administrative Privileges, Elevated

Is Developer Mode enabled?

None

Relevant log/console output

No response

Debug Output

Running NVM for Windows with administrator privileges.

Administrator: Command Prompt (Admin) - nvm  debug
Windows Version: 10.0 (Build 22631)

NVM4W Version:      1.1.12
NVM4W Path:         C:\Users\usr\AppData\Roaming\nvm\nvm.exe
NVM4W Settings:     C:\Users\usr\AppData\Roaming\nvm\settings.txt
NVM_HOME:           C:\Users\usr\AppData\Roaming\nvm
NVM_SYMLINK:        C:\Program Files\nodejs
Node Installations: C:\Users\usr\AppData\Roaming\nvm

Total Node.js Versions: 0
Active Node.js Version: none
(run "nvm use <version>" to activate a version)
NVM_SYMLINK does not exist yet. This is auto-created when "nvm use" is run.

IPv6 is enabled. This can slow downloads significantly.

No problems detected.

Find help at https://github.com/coreybutler/nvm-windows/wiki/Common-Issues

Anything else?

No response

[coreybutler]

Are you sure you ran nvm list available? Could you have inadvertently run nvm install list-available? I ask because that's the only way I can reproduce the error with that exact URL. SHASUMS are only retrieved during the install process, so there isn't another time when that would be requested.

Here's nvm install list-available (which should fail since there is no alias called list-available) followed by nvm list available (which should display a table).

[Leozw12]

Hi @coreybutler ，I have the same problem. It doesn't seem to use the version I specified to find node.

[coreybutler]

@Leozw12 it looks like you're using a mirror instead of the official node releases. The mirror doesn't appear to have that file.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.