Skip to content

fix: accept nvm reshim --force and resign PNPM_HOME launchers - #27

Merged
coreybutler merged 1 commit into
mainfrom
fix/reshim-force-flag
Nov 2, 2026
Merged

coreybutler merged 1 commit into
mainfrom
fix/reshim-force-flag

Conversation

@coreybutler

Copy link
Copy Markdown
Contributor

Summary

  • Accept nvm reshim --force so the flag matches reshim.exe hint text (sync already always forces).
  • Re-sign PNPM_HOME\bin\pnpm.cmd after nvm firewall trust module pnpm for standalone installs.

Fixes nvm-windows/nvm#1526 (item 3 + trust resign for standalone).

Test plan

  • go test ./test/commands/ -run TestCLIReshim
  • nvm reshim --force no longer reports unknown flag

Kong rejected --force even though sync always forces reshim.exe; accept
the flag for the documented hint. Also re-sign PNPM_HOME\bin pnpm.cmd
after firewall trust module so standalone installs match npm globals.
@coreybutler
coreybutler merged commit 385e966 into main Nov 2, 2026
5 of 6 checks passed
@coreybutler
coreybutler deleted the fix/reshim-force-flag branch November 2, 2026 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Shim mode falls back to Corepack instead of standalone pnpm 12; NVM4306 persists after trusting pnpm

1 participant