Home›Error Fixes

npm / npx Is Not Recognized

Fix npm or npx is not recognized by checking node, npm and npx in the same terminal, repairing Node.js, and separating PATH errors from PowerShell policy errors.

On this page

First, match npm / npx is not recognized

This page targets npm / npx is not recognized. The full message can contain a few extra words on different operating systems or Node.js versions, but the core error code or phrase should match.

npm / npx is not recognized

'npx' is not recognized

'npm' is not recognized

npx command not found

npm command not found

When searching or asking for help, copy the full error and remove API keys, private repository names, usernames and sensitive paths.

Fast fix: npm / npx is not recognized

Run node --version, npm --version and npx --version in the same terminal. If node works but npm or npx is missing, repair the Node.js installation and reopen the terminal. If the exact error says npm.ps1 cannot be loaded, use the PowerShell-specific guide instead.

What npm / npx is not recognized means

Node may be installed, but its npm or npx command is missing from PATH, the installation is incomplete, or PowerShell is blocking the script shim.

Common causes of npm / npx is not recognized

The Node.js installation is incomplete and does not include npm correctly.
PATH contains node.exe but not the npm command directory.
A Node version manager points to an incomplete version.
The current terminal still has an old PATH.
PowerShell is blocking npm.ps1 or npx.ps1 because of its execution policy.

Source trace for npm / npx is not recognized

These links are pinned to the 0.1.2-alpha.5 / 49a606b snapshot used for this page. They help separate npm / npx is not recognized from failures produced by Node.js, PowerShell, the operating-system network stack or filesystem permissions.

Official npm launch pathThe official quick start is npx @deepseek-ai/dsh web. If npm or npx is not found, the failure occurs before DSH starts and belongs to the Node/npm installation path.

Fix npm / npx is not recognized

01
Check all three commands
Run them in the same terminal so you know which layer is failing.
node --version npm --version npx --version
02
Read the exact PowerShell message
If it says npm.ps1 or npx.ps1 cannot be loaded because scripts are disabled, do not reinstall Node first. Open the related PowerShell guide.
03
Repair the Node.js installation
Use the official Node installer or your Node version manager to reinstall a supported version with npm included.
04
Open a new terminal
Close all existing shells and editor terminals so they inherit the repaired PATH.
05
Retry the DSH command
Continue only after npm and npx both return versions.
npx @deepseek-ai/dsh web

Verify npm / npx is not recognized is fixed

npm --version and npx --version both return values.
The same terminal can start the DSH quick start.

What to avoid

Do not install a random standalone npx package to hide a broken Node installation.
Do not use administrator permissions as the first fix for a PATH problem.
Do not confuse a PowerShell execution-policy error with a missing npm installation.