Windows repair note

Fix: npm is not recognized in PowerShell

This is a Runtime / PATH failure. Fix it before running npm install, Electron rebuilds, node-gyp, or project cleanup commands, because every later error can be noise while PowerShell cannot find npm.

npm : The term 'npm' is not recognized as the name of a cmdlet
Run the free diagnostic Get the full recovery kit
1

Open a fresh terminal first

After installing Node.js, old PowerShell and VS Code terminals may not load the updated PATH. Restart the terminal before changing anything else.

node -v
npm -v
2

Check PowerShell command resolution

Use Get-Command and where.exe. In PowerShell, bare where can be interpreted as an alias instead of Windows executable lookup.

Get-Command node -ErrorAction SilentlyContinue
Get-Command npm -ErrorAction SilentlyContinue
Get-Command npm.cmd -ErrorAction SilentlyContinue
where.exe node
where.exe npm
3

Check npm.cmd if npm fails

If node works but npm does not, verify whether npm.cmd exists in the Node.js install directory.

npm.cmd -v
Test-Path "C:\Program Files\nodejs\node.exe"
Test-Path "C:\Program Files\nodejs\npm.cmd"
$env:Path -split ';' | Select-String -SimpleMatch 'nodejs'
4

Only then run project commands

Once npm is visible, move to the project folder and check package.json before installing dependencies.

cd C:\path\to\your\project
Test-Path .\package.json
npm install
npm run dev

When to use the paid kit

If the quick checks do not get the app running, the full WiaiKit recovery kit gives the ordered Windows path for npm, Electron, native modules, Visual Studio Build Tools, and Push-to-Talk setup.

Node.js PATHPowerShell command resolutionVS Code terminalnpm.cmd

Get the recovery kit for 13 USD

Independent practical material. Not an official OpenAI, Codex, Electron, Node.js, or OpenWhispr product.