Home›Error Fixes

'node' Is Not Recognized

Fix 'node' is not recognized by installing a supported Node.js version, reopening the terminal, checking PATH, and verifying node and npm before DSH.

On this page

First, match 'node' is not recognized

This page targets 'node' 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.

'node' is not recognized

node is not recognized as an internal or external command

node command not found

node is not recognized / 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: 'node' is not recognized

Use Node.js 24 or later, or Node.js 22.19 or later within the 22.x line. Node.js 23 does not satisfy the official DSH engine range. After installing, close every terminal, open a new one and run node --version.

What 'node' is not recognized means

The current terminal cannot find the Node.js executable, so npm, npx and the DSH CLI cannot run.

Common causes of 'node' is not recognized

Node.js is not installed.
The installer did not add Node to PATH.
The terminal was opened before Node was installed.
A Node version manager points to an old or incomplete installation.
Node.js 23 is installed even though it is outside the supported engine range.

Source trace for 'node' is not recognized

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

Node engine contractThe repository declares Node.js ^22.19.0 or >=24.0.0. A shell that cannot resolve node has not reached the DSH runtime yet, so PATH or Node installation must be fixed first.

Fix 'node' is not recognized

01
Install a supported Node.js version
The official DSH source requires ^22.19.0 or >=24.0.0. A simple choice is Node.js 24 or later. Node.js 22 is also valid only from 22.19.0 upward; Node.js 23 is not supported by this range.
02
Close and reopen every terminal
Close PowerShell, Command Prompt, Terminal and editor terminals. Open a new terminal so it receives the updated PATH.
03
Check Node and npm
Both commands must work in the same terminal before you try DSH.
node --version npm --version
04
Find which Node executable is being used
On Windows, use where.exe. This helps identify an older duplicate installation.
where.exe node
05
Find Node on macOS or Linux
Use command -v to see the executable selected by your shell.
command -v node
06
Start DSH only after the checks pass
When Node and npm work and the version is supported, run the official quick start.
npx @deepseek-ai/dsh web

Verify 'node' is not recognized is fixed

node --version returns 22.19.x or later within 22.x, or 24.x or later.
npm --version succeeds in the same terminal.
npx starts downloading or launching DSH.

What to avoid

Do not use Node.js 23 for DSH.
Do not debug DSH provider or workspace settings before Node works.
Do not keep using a terminal that was open before Node was installed.