DEV Community: Tony Stark

Fix npm is not recognized in PowerShell on Windows

Tony Stark — Wed, 24 Jun 2026 13:35:01 +0000

If PowerShell shows this after you installed Node.js:

npm : The term 'npm' is not recognized as the name of a cmdlet, function, script file, or operable program.

do not start by reinstalling your project.

This is usually a Runtime / PATH problem. Until Windows can find npm, later errors from Electron, node-gyp, better-sqlite3, or a voice coding app are just noise.

Here is the order I would use.

1. Open a fresh PowerShell window

If Node.js was installed while PowerShell or VS Code was already open, the old terminal may not see the updated PATH.

Close PowerShell. If you are using VS Code, close and reopen VS Code too.

Then run:

node -v
npm -v

If both work, you do not need to repair anything else at this layer.

2. Check command resolution the PowerShell way

Use Get-Command first:

Get-Command node -ErrorAction SilentlyContinue
Get-Command npm -ErrorAction SilentlyContinue
Get-Command npm.cmd -ErrorAction SilentlyContinue

Then use where.exe, not bare where:

where.exe node
where.exe npm

In PowerShell, where can be interpreted as an alias for Where-Object. where.exe asks Windows directly where the executable is.

Common mistake:

where npm

Better:

where.exe npm

That small .exe matters when you are debugging Windows command resolution from PowerShell or a VS Code terminal.

3. If node works but npm does not

Try:

npm.cmd -v
Get-Command npm.cmd -ErrorAction SilentlyContinue

If npm.cmd works but npm does not, the Node install may be present but command resolution or PATH order is wrong.

Common expected locations look like:

C:\Program Files\nodejs\node.exe
C:\Program Files\nodejs\npm.cmd

Do not paste random PATH edits yet. First confirm whether those files exist:

Test-Path "C:\Program Files\nodejs\node.exe"
Test-Path "C:\Program Files\nodejs\npm.cmd"

4. Check PATH only after the files exist

$env:Path -split ';' | Select-String -SimpleMatch 'nodejs'

If C:\Program Files\nodejs is missing from PATH, repair the Node.js installation or add the path through Windows Environment Variables.

After changing PATH, open a new PowerShell window and retest:

node -v
npm -v
where.exe node
where.exe npm

5. Only then run project commands

When Runtime is fixed, go back to the project folder:

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

If package.json is missing, you are in the wrong folder.

If Electron or native modules fail after this, that is a different layer.

Free diagnostic

I maintain a read-only Windows diagnostic for this exact class of setup failure:

Run the free Windows AI coding setup diagnostic

It checks:

Runtime: Node.js, npm, PATH
Project folder and package.json
Electron install state
Native modules such as better-sqlite3
Visual Studio Build Tools detection
Voice coding stack indicators

GitHub repo:

WiaiKit Windows AI Coding Setup Repair

The script is read-only. It does not install, delete, or modify files.

Recovery order

For npm is not recognized in PowerShell, use this order:

Open a fresh PowerShell or VS Code terminal.
Run node -v and npm -v.
Run Get-Command node, Get-Command npm, and Get-Command npm.cmd.
Run where.exe node and where.exe npm.
Confirm C:\Program Files\nodejs\npm.cmd exists.
Repair Node.js PATH if needed.
Only then run npm install inside the project.

Related free page:

Fix npm is not recognized in PowerShell on Windows

The paid WiaiKit repair kit is the longer recovery path after the diagnostic tells you which layer is broken: npm PATH, Electron, node-gyp, Visual Studio Build Tools, native modules, OpenWhispr, Codex, Claude Code, and push-to-talk voice workflows.

Fix node-gyp Visual Studio Build Tools errors on Windows

Tony Stark — Wed, 24 Jun 2026 07:01:21 +0000

If you see this on Windows:

node-gyp error Could not find any Visual Studio installation to use

do not start by reinstalling everything.

node-gyp usually appears after a package falls back to local native compilation. The useful question is not "how do I reinstall Node?" It is:

Which layer is broken: npm, the project folder, Electron, a native module, or Visual Studio Build Tools?

Here is the order I use.

1. Confirm Node and npm first

Run this in a fresh PowerShell window:

node -v
npm -v
where node
where npm

If npm is not recognized, fix that before touching Build Tools. A broken PATH can make every later error misleading.

2. Confirm you are in the project root

Get-Location
Test-Path .\package.json
Test-Path .\node_modules

If package.json is missing, you are in the wrong folder.

If node_modules is missing, run:

npm install

Then read the first real error. Do not jump straight to Visual Studio.

3. Identify the package that is compiling

Run:

npm install
npm rebuild
npm ls node-gyp
npm ls better-sqlite3

Look in the log for:

node-gyp
prebuild-install
MSBuild
cl.exe
Windows SDK
VCBuild

If the package is better-sqlite3, windows-key-listener, or another native module, the fix depends on the Node/Electron version combination. It may need a compatible prebuilt binary or an Electron-compatible rebuild, not just Visual Studio.

4. Check whether Visual Studio C++ tools are detected

& "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe" -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath

If this prints a path, C++ tools are visible.

If it prints nothing, Visual Studio Build Tools may be missing the C++ workload.

Check npm's Visual Studio setting:

npm config get msvs_version
npm config get python

A stale msvs_version can point npm/node-gyp at an older toolchain.

5. Install or repair Build Tools only if the log requires it

In Visual Studio Installer, the usual workload is:

Desktop development with C++
MSVC C++ x64/x86 build tools
Windows 10 or Windows 11 SDK

After installing or repairing it, open a new PowerShell window and rerun:

node -v
npm -v
& "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe" -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath
npm rebuild
npm run dev

If it still fails, stop reinstalling Visual Studio and go back to the exact package that is compiling.

Free diagnostic

I made a read-only Windows diagnostic for this kind of setup failure:

Run the free Windows AI coding setup diagnostic

It checks the layers in order:

Runtime: Node.js, npm, PATH
Project: folder, package.json, node_modules
Electron: install hook and binary
Native modules: better-sqlite3, key listeners, node-gyp
Build Tools: Visual Studio C++ toolchain
Voice coding stack: Windows audio, WSL, Codex, Claude Code, OpenWhispr

The script is read-only. It does not install, delete, or modify files.

GitHub repo:

https://github.com/wiaikit/wiaikit-windows-ai-coding-setup-repair

Paid recovery path

The paid WiaiKit repair kit is the longer layer-by-layer recovery path after the diagnostic tells you what is broken: npm PATH, Electron, node-gyp, Visual Studio Build Tools, native modules, OpenWhispr, Codex, Claude Code, and push-to-talk voice workflows.

For this specific node-gyp error, start with the free diagnostic above.

Fix Electron failed to install correctly on Windows

Tony Stark — Tue, 23 Jun 2026 14:05:53 +0000

If you are on Windows and an Electron app stops with this error:

Electron failed to install correctly, please delete node_modules/electron and try installing again

the important detail is usually this:

node_modules/electron can exist while the actual Electron binary is missing.

So a blind npm install retry is not always enough. First check whether the package folder exists and whether electron.exe was actually downloaded.

Fast path: check this before reinstalling everything

In the project folder, run this first:

Test-Path .\package.json
Test-Path .\node_modules\electron
Test-Path .\node_modules\electron\dist\electron.exe

The key line is the third one.

If node_modules\electron is True but node_modules\electron\dist\electron.exe is False, the package is present but the Electron binary is missing. In that case, start with the targeted Electron reinstall below before deleting the whole node_modules folder.

1. Confirm you are in the project folder

Open PowerShell in the project folder and run:

Get-Location
Test-Path .\package.json
Test-Path .\node_modules\electron

You want:

True
True

for package.json and node_modules\electron.

If package.json is False, you are in the wrong folder. Move to the app folder first.

2. Check the actual Electron binary

Now check the binary:

Test-Path .\node_modules\electron\dist\electron.exe

If this returns False, Electron's package directory exists, but the install hook or binary download did not complete.

That is the state that often triggers:

Electron failed to install correctly

Common reasons on Windows:

the Electron postinstall step was interrupted;
the Electron binary download was blocked by a network, antivirus, corporate proxy, or TLS inspection;
npm install ran in an old terminal after Node.js or PATH changed;
the app also has native modules, so the Electron error is the first visible failure but not the only broken layer.

3. Try the targeted repair first

Before deleting all node_modules, try the smaller fix:

Remove-Item -Recurse -Force .\node_modules\electron
npm install

Then check again:

Test-Path .\node_modules\electron\dist\electron.exe

If it returns True, retry your app:

npm run dev

4. If Electron still does not install, check Node and npm

Run:

node -v
npm -v
where node
where npm

On Windows, a fresh Node.js install can update PATH, but the old PowerShell window may not see the change yet.

If node works but npm does not, close PowerShell and open a new one before reinstalling anything.

5. If native modules are involved, do not guess

Electron apps often include native packages such as:

better-sqlite3
node-gyp
Windows key listeners
SQLite bindings

Those packages can require prebuilt binaries or local build tools.

Check what is actually present:

npm ls better-sqlite3
npm ls node-gyp

If the project needs a local build, Windows may need Visual Studio Build Tools. But do not install the whole toolchain blindly. First confirm the package that is failing and whether a prebuilt binary exists for your Node/Electron version.

6. Free layered diagnostic script

I published a small read-only diagnostic script for this class of Windows setup problems:

GitHub: WiaiKit Windows AI Coding Setup Repair

It now checks the setup by layer:

Runtime: Node.js, npm, PATH
Project: package.json, node_modules
Electron: package folder, electron.exe, install hook
Native modules: better-sqlite3, key listeners, node-gyp
Build Tools: Visual Studio C++ toolchain
Voice stack: Windows audio, WSL, Codex, Claude Code indicators

Run it from the project folder:

powershell -ExecutionPolicy Bypass -File .\wiaikit-windows-ai-coding-setup-check.ps1

Or pass the project path:

powershell -ExecutionPolicy Bypass -File .\wiaikit-windows-ai-coding-setup-check.ps1 -ProjectPath C:\path\to\your\project

The script does not install, delete, or modify files. It prints OK, CHECK, BROKEN, and NEXT ACTION lines so you can stop guessing which layer failed.

Browser version:

Run the free Windows AI coding setup diagnostic

7. My usual recovery order

For this specific error, I would use this order:

Confirm the folder has package.json.
Check node_modules\electron.
Check node_modules\electron\dist\electron.exe.
Delete only node_modules\electron.
Run npm install.
Only then consider a full node_modules reinstall.
If native modules fail, inspect node-gyp, Visual Studio Build Tools, and the exact package.

This avoids the common Windows loop of reinstalling everything without knowing what actually broke.

Related diagnostic page

I also keep the same fix as a shorter checklist here:

Fix Electron failed to install correctly on Windows

For this specific Electron error, start with the free diagnostic above.

When Win+H Is Not Enough: Push-to-Talk Voice Tasks for Codex on Windows

Tony Stark — Tue, 23 Jun 2026 07:28:16 +0000

Win+H is fine for simple dictation. This setup is for people who want a repeatable Push-to-Talk workflow for sending spoken tasks into Codex on Windows.

The idea is to use OpenWhispr as the voice input layer: you speak the task, OpenWhispr turns it into text, and that text becomes the prompt or instruction you use with Codex.

The target workflow is simple:

Press a Push-to-Talk key.
Dictate the task.
Let OpenWhispr transcribe it locally or through the configured model.
Paste or pass the text into Codex.

Why not just use Win+H?

For normal dictation, Windows voice typing is the easiest option. Press Win+H, speak into a text field, and Windows enters the text.

This setup is for a different use case:

you want Push-to-Talk behavior instead of a general dictation popup;
you are building a repeatable voice loop specifically around Codex tasks;
you want OpenWhispr in the workflow, not only the built-in Windows dictation layer;
you are running into Windows setup errors around Node.js, npm, Electron, native modules, or key listeners;
you want recovery commands when the local Electron/npm environment breaks.

So the point is not “better than Win+H for everyone.” The point is “more useful when you are trying to build a Codex voice workflow on Windows.”

The difficult part is not the idea. The difficult part is getting the Windows setup into a clean state when Node.js, npm, Electron native modules, Visual Studio Build Tools, or key listeners fail.

This is the troubleshooting order I would use before reinstalling everything blindly.

1. Check that Node.js and npm are actually available

If PowerShell says:

npm : The term 'npm' is not recognized as the name of a cmdlet, function, script file, or operable program.

First check:

node -v
npm -v
where node
where npm

For current OpenWhispr-style Electron setups, use Node.js 24+ if the project requires it. If node works but npm does not, restart PowerShell after installing Node.js because PATH changes may not be loaded in the old terminal session.

2. Reinstall dependencies from a clean local state

If the project has a broken node_modules folder, do not keep retrying npm run dev first. Clean the local install and reinstall.

Remove-Item -Recurse -Force .\node_modules
Remove-Item -Force .\package-lock.json
npm install

If the project depends on native modules, watch the install output. Modules such as SQLite bindings or key listeners may need prebuilt binaries or local compilation.

3. Fix Electron install failures

This error usually means the electron package exists in node_modules, but the Electron binary did not download or unpack correctly:

Electron failed to install correctly, please delete node_modules/electron and try installing again

Try a targeted reinstall first:

Remove-Item -Recurse -Force .\node_modules\electron
npm install electron

If that still fails, clean all dependencies:

Remove-Item -Recurse -Force .\node_modules
npm cache verify
npm install

If you are behind a VPN, corporate proxy, antivirus inspection, or unstable connection, Electron downloads can fail even when npm itself works.

4. Understand Visual Studio Build Tools

Some npm packages include native code. On Windows, native modules may require C/C++ build tooling.

The common choices are:

Visual Studio Build Tools with C++ workload
MinGW-w64 for some projects
a prebuilt binary if the package publishes one for your Node/Electron version

If a package already has a compatible prebuilt binary, you may not need local compilation. If not, the install step can fail until build tools are installed.

5. Understand `windows-key-listener fallback mode`

For Push-to-Talk, a Windows key listener may need native access to keyboard events.

If you see:

[windows-key-listener] Push-to-Talk will use fallback mode
[windows-key-listener] To compile locally, install Visual Studio Build Tools or MinGW-w64

It means the app can still run, but Push-to-Talk may use a less direct fallback mode unless the native listener is compiled or available.

This does not always block the whole app. It usually affects the quality or reliability of hotkey handling.

6. Start the app after dependency recovery

After dependency repair:

npm install
npm run dev

If the project downloads models or binaries during npm run dev, let those scripts finish. A partially downloaded model or binary can create confusing follow-up errors.

7. Keep the goal clear

The goal is not just “make npm install pass.”

The actual goal is to get a usable voice-driven loop on Windows:

microphone input
speech-to-text through OpenWhispr
Push-to-Talk or a workable fallback
clean text ready for Codex
repeatable setup commands if Windows breaks the environment again

Free diagnostic first

I also published a free read-only diagnostic script for this setup class:

GitHub: WiaiKit Windows AI Coding Setup Repair

It checks the setup by layer:

npm is not recognized
Electron failed to install correctly
node-gyp / Visual Studio Build Tools native module issues
better-sqlite3 and other native modules
windows-key-listener fallback mode
voice coding stack indicators

Run it before buying anything:

Invoke-WebRequest https://raw.githubusercontent.com/wiaikit/wiaikit-windows-ai-coding-setup-repair/main/wiaikit-windows-ai-coding-setup-check.ps1 -OutFile .\wiaikit-windows-ai-coding-setup-check.ps1
powershell -ExecutionPolicy Bypass -File .\wiaikit-windows-ai-coding-setup-check.ps1 -ProjectPath C:\path\to\your\project

Browser version: https://pay.wiaikit.com/free?lang=en

Paid repair kit

The paid WiaiKit repair kit is for the longer path after the diagnostic tells you which layer is BROKEN or needs CHECK.

It includes the ordered recovery path for npm PATH, Electron install failures, node-gyp, Visual Studio Build Tools, native modules, OpenWhispr, Codex, Claude Code, and push-to-talk voice workflows.

Paid repair kit page: https://pay.wiaikit.com

If you only need the general troubleshooting direction, the notes above and the free diagnostic should already help. The ZIP is for people who want the compact ordered recovery path.

DEV Community: Tony Stark

Fix npm is not recognized in PowerShell on Windows

1. Open a fresh PowerShell window

2. Check command resolution the PowerShell way

3. If node works but npm does not

4. Check PATH only after the files exist

5. Only then run project commands

Free diagnostic

Recovery order

Fix node-gyp Visual Studio Build Tools errors on Windows

1. Confirm Node and npm first

2. Confirm you are in the project root

3. Identify the package that is compiling

4. Check whether Visual Studio C++ tools are detected

5. Install or repair Build Tools only if the log requires it

Free diagnostic

Paid recovery path

Fix Electron failed to install correctly on Windows

Fast path: check this before reinstalling everything

1. Confirm you are in the project folder

2. Check the actual Electron binary

3. Try the targeted repair first

4. If Electron still does not install, check Node and npm

5. If native modules are involved, do not guess

6. Free layered diagnostic script

7. My usual recovery order

Related diagnostic page

When Win+H Is Not Enough: Push-to-Talk Voice Tasks for Codex on Windows

Why not just use Win+H?

1. Check that Node.js and npm are actually available

2. Reinstall dependencies from a clean local state

3. Fix Electron install failures

4. Understand Visual Studio Build Tools

5. Understand windows-key-listener fallback mode

6. Start the app after dependency recovery

7. Keep the goal clear

Free diagnostic first

Paid repair kit

5. Understand `windows-key-listener fallback mode`