[issue] v2.0.1-hotfix.1: npm install -g <package> fails to trigger reshim for global packages

[TinyPeanut]

Issue Summary

In v2.0.1-hotfix.1, npm install -g <package> fails to trigger the automatic reshim process, making globally installed CLI tools (e.g., commitizen, @anthropic-ai/claude-code) uncallable.

Steps to Reproduce

1. Run npm install -g commitizen
2. Attempt to run cz --version

Actual Behavior

• Terminal reports the command is not recognized.
• No corresponding shim files are generated in the .shim directory for the newly installed packages.
• Manually running nvm reshim successfully resolves the issue and makes the command callable.

Expected Behavior

Global npm packages should be automatically shimmed and invocable immediately after installation.

Environment

• OS: Windows [11]
• nvm-windows version: v2.0.1-hotfix.1 (custom node path)
• Node.js version: [22.23.2]

[coreybutler]

Thanks for the clear repro.

This was a regression. After npm install -g, the proxy was spawning reshim.exe directly. The .shim directory is ACL-locked, so the new hardlinks were silently failing. nvm reshim worked because it "unlocks" .shim first before running reshim.

It's been fixed in main and will be published in the next hotfix.

Note

Fix: Post-global install now goes through nvm.exe --reshim, which opens the write window before creating shims.

I'll close this once the hotfix is released.

[coreybutler]

https://github.com/nvm-windows/nvm/releases/tag/v2.0.1-hotfix.2

[TinyPeanut]

https://github.com/nvm-windows/nvm/releases/tag/v2.0.1-hotfix.2

The latest release has fixed the reshim problem.
Thanks for your hard work!

[coreybutler]

Thanks for your feedback/support @TinyPeanut. I greatly appreciate the time you've taken to open issues and confirm their fixes.