[Issue]: nvm run.cmd in %nvm_home% has a hardcoded path

[KurzedMetal]

What happened?

I ran by mistake run xyz instead of npm run xyz and got a weird error message generated by nvm's run.cmd exposed through %nvm_home% in PATH env variable.

Even tho I made a mistake, I don't think nvm should be exposing commands that a normal user shouldn't use (like development helper scripts/commands, etc), and definitely not a script that has a hardcoded path to the developer's OneDrive folder 😄

There are other scripts like "elevate", "install", "setuserenv", "uninst000", etc; that are being exposed by the PATH and I'm not sure if that's intended.

Sorry I'm not including an image of the output, I'm reporting from a computer that doesn't nvm installed.

What did you expect to happen?

Less development scripts exposed through %nvm_home% PATH
Minimal exposed scripts through PATH. Does user ever need anything else other than nvm.exe?
No exposed scripts with hardcoded directories that only a nvm developer can use.

Version

1.2.0 or newer (Default)

Which version of Windows?

Windows 11+ (Default)

Which locale?

English (Default)

Which shell are you running NVM4W in?

Command Prompt

User Permissions?

Administrative Privileges, Elevated

Is Developer Mode enabled?

No (Default)

Relevant log/console output

No response

Debug Output

Not needed

Anything else?

No response

[github-actions]

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]

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

[VAllens]

灾难性更新

[VAllens]

This is a rookie mistake that no developer should ever make, because hard-coding paths is extremely foolish.

[coreybutler]

This file was for testing purposes. It didn't get stripped out of the prod build. It won't be there when I release v1.2.3.