nvm stopped working in vscode terminal

[keaedwar]

My nvm for windows installation has been working great for months, but lately (like for a week or two) when I run a "npm run serve" in a vscode terminal, I get the error

'vite' is not recognized as an internal or external command, operable program or batch file.

If I use cross-env or get rid of cross-env and use vitest directly, then whatever command I use can't be found either. The package.json has these in the scripts

"serve": "vite dev --port 8080",
"test:unit": "cross-env NODE_OPTIONS='' vitest",

According to AI, it looks like this is happening because

• NVM for Windows: Node.js managed by NVM isn't available in cmd.exe PATH
• npm scripts: npm uses cmd.exe internally, not PowerShell
• PATH resolution: Local .\node_modules\.bin wasn't accessible without full Node.js path

So, if I prefix each script with the full path to node.exe (which is C:\Users\%USERNAME%\Roaming\nvm\nodejs\node.exe) it works, which isn't ideal for a CI/CD system.

The odd thing is bullet point 1 (availability in cmd.exe) seems to only be true in vscode (if I run a cmd.exe in Windows, it works fine, just not in vscode).

I did put an issue into vscode (nvm's nodejs stopped working in vscode terminal), but has anyone else seen this in their Windows environment with vscode?

[keaedwar]

It's a known problem in vscode that is now fixed. see issue here.