Node.js for Claude Code: Version Requirements and Setup

You only need Node.js for Claude Code if you install the CLI through npm — the native installer ships a standalone binary with zero dependencies. The npm route historically required Node 18+, and as of v2.1.198 the package asks for Node 22+. Check yours with node --version; install or update through nvm.

We run this site with Claude Code every day — a Windows desktop, a MacBook, and two Linux runners — so we've hit every Node-related install failure the forums complain about. The good news is that most of them are now optional: since Anthropic shipped the native installer, Node stopped being a hard dependency. Below: what the official Claude Code requirements actually say, which Node version clears the bar, per-platform setup with nvm, and a fix table for the errors that still bite. New to the tool itself? Start with our pillar, What Is Claude Code?

Does Claude Code actually require Node.js?

Only on one install path. Anthropic's official setup documentation lists the Claude Code requirements as macOS 13+, Windows 10 1809+, or Ubuntu 20.04+/Debian 10+, 4 GB of RAM, and an internet connection. Node.js is not on the list. The recommended native installer downloads a self-contained binary, wires up your PATH, and auto-updates in the background:

# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

The npm route is the legacy one. Anthropic deprecated it at v2.1.15 in favor of the native build, and the docs now file it under "advanced installation options." Here's the detail most people miss: the npm package installs the same native binary the standalone installer ships. npm pulls it in through a per-platform optional dependency and links it into place — your Node runs the installation, not Claude Code itself.

So the question of Node for the CLI splits cleanly. Fresh machine with no Node opinions: use the native installer and this whole problem class disappears. Existing toolchain where every global tool flows through npm: the legacy route still works, provided your Node version clears the bar below.

What version of Node for the CLI do you need?

The Node for the CLI version floor has moved twice. The original requirement was Node 18 or newer — that's where the "Claude Code requires Node.js version 18 or higher" message everyone has googled comes from. As of v2.1.198, the npm package declares Node 22+ in its engines field. And because the binary it installs never invokes your Node at runtime, an older version prints an EBADENGINE warning during install rather than failing — the install completes and claude still runs.

Checking your Claude Code Node version pairing takes one command each:

node --version   # your Node runtime
claude --version # your Claude Code build

Then match your Node against the current lines:

Our advice: forget the old Claude Code Node 18 floor entirely. Node 18 stopped receiving security patches in April 2025, so even though the CLI would tolerate it, nothing else on your machine should. Install 22 or 24 and both the historical and the current requirement are cleared at once.

How to install Node for the CLI on Windows, macOS, and Linux

When we set up Node.js for Claude Code on a new machine, we reach for a version manager, never a system-wide package. nvm installs Node into your home directory, which means no sudo, no root-owned npm prefix, and none of the EACCES permission failures that plague global installs. You install Node for Claude Code once, then switching or updating versions is one command:

nvm install --lts            # newest long-term-support Node
nvm use --lts
nvm alias default 'lts/*'    # every new shell starts on LTS

The same three commands give you a Node.js for Claude Code setup that survives OS upgrades and project version pins without breaking the CLI.

Three version-manager lessons we learned the hard way:

1. Set the default alias. Without it, new shells — and GUI apps like VS Code launched from the dock — start with no Node on PATH at all. That single omission causes most "extension can't find Node" reports.
2. Global packages don't follow you between versions. nvm keeps a separate global folder per Node line, so jumping from 18 to 22 makes an npm-installed claude vanish. Reinstall it under the new version, or use nvm install --reinstall-packages-from=18.
3. Never sudo npm install -g. Anthropic's docs warn against it explicitly. One sudo install leaves root-owned files in your prefix, and every future update fails with permission errors until you fix ownership.

Node-related Claude Code failures and their fixes

When Node.js for Claude Code goes wrong, the failures cluster into three groups: install-time errors from npm, launch-time errors from PATH, and runtime crashes. Work the table, then verify with claude doctor.

One Windows-specific footnote: Claude Code prefers Git Bash for its shell tool, so a missing Git for Windows produces confusing failures that look Node-shaped but aren't. Install Git, or let the CLI fall back to PowerShell.

Verify the setup with claude doctor

claude --version proves the binary launches; claude doctor proves the setup is healthy. It reports your install type and version, the result of the last auto-update attempt, auth state, and config problems — and on npm installs it flags an unwritable global directory before that blocks your next update, listing the available fixes. We run it after every machine setup and after any Node change; the full command reference lives in our Claude Code CLI documentation guide.

Two closing habits keep the whole Node.js for Claude Code stack boring, which is the goal. First, update deliberately: claude update on demand, or trust the native installer's background updates. Second, if terminal plumbing is exactly what you're trying to avoid, the Claude Code Desktop app skips the CLI setup entirely — same agent, graphical shell, no PATH to debug.

Claude pricing at a glance

For the full breakdown of every plan, see our how much Claude costs guide.