Claude Code updates to drop JS in favor of native binary, saying goodbye to Node.js dependency

Anthropic has upgraded Claude Code’s distribution method to v2.1.113: the npm package is changed from JavaScript code to pre-compiled native binary executables for each platform, rather than JavaScript source code. This version changes the npm package from JavaScript code to pre-compiled native binary executables for each platform, eliminating the hidden cost of waiting for the Node.js process and JIT warm-up every time it starts.
(Background: Deep dive into Claude Opus 4.7’s coding capabilities upgrade, 1M with no extra charge—what are the drawbacks found in real testing?)
(Additional background: Anthropic launches the visual design powerhouse “Claude Design”! In one sentence, instantly create presentations, proposals, and app prototypes)

Table of Contents

Toggle

• What changed in this version?
• Technical perspective: What’s the difference between the two approaches?
• What changes in practice?
• What do users need to do?
• A bigger trend: CLI tools moving toward native execution

Every time you press claude, the system keeps repeating the same thing: start Node.js, load all JavaScript script files, complete JIT warm-up, and then enter the CLI main loop.

This latency isn’t a big deal for Web servers that run for a long time, but for CLI tools that are called again and again, you have to rerun everything from scratch each time. After dozens of calls a day, this waiting time becomes the most annoying performance issue. Anthropic solves it with a single built-in update.

What changed in this version?

Starting from v2.1.113, what you get after running npm install -g @anthropic-ai/claude-code has changed.

At the surface level, the command hasn’t changed at all; underneath, the npm package no longer distributes JavaScript code. Instead, it pulls the corresponding pre-compiled native binary executable based on the user’s operating system (macOS / Linux / Windows, ARM / x86), and then links it to the correct location via a postinstall script.

User-side installation process: one command—everything remains the same.

Technical perspective: What’s the difference between the two approaches?

Startup path for the JS version (before v2.1.113)

Every time the user runs claude, the system goes through four steps:

• Launch the Node.js program: the operating system starts the Node.js runtime environment
• Load the scripts: Node.js reads all .js files of Claude Code
• JIT warm-up: the just-in-time compiler compiles JavaScript into machine code
• Enter the CLI main loop: this is when the actual work begins

Startup path for the native binary (starting from v2.1.113)

At the time of release, Anthropic bundles the JavaScript engine and all the code into a single executable file, compiled separately for each platform. What the operating system receives is a native format it recognizes: it loads and runs directly, skipping all the overhead of starting Node.js and doing JIT warm-up.

What changes in practice

For heavy users who run claude dozens of times a day, the disappearance of startup delay is an improvement you can feel directly.

What do users need to do?

Nothing at all. Just keep using the existing command:

npm install -g @anthropic-ai/claude-code

npm automatically selects the appropriate native binary for your platform behind the scenes, so users don’t need to notice any changes.

If you want to keep using the JS version

Special requirements (such as running on a platform without pre-compiled binaries available) allow you to pin the version number:

npm install -g @anthropic-ai/[email protected]

A bigger trend: CLI tools moving toward native execution

This isn’t Anthropic’s invention; it’s a common direction of evolution for toolchains. CLI tools in the Rust ecosystem (ripgrep, fd) and Go tools (gh, terraform) have long distributed native binaries directly, avoiding dependencies on external runtimes when executed.

The JavaScript ecosystem used to rely on running under Node.js, but as tool complexity increases and usage frequency rises, Node.js’s startup cost has gradually shifted from “acceptable” to “a clear obstacle.” Anthropic’s choice this time is to bundle the JS engine directly, so users no longer need to perceive the runtime during execution.

For developers who rely on Claude Code every day, hidden behind this small version bump is a genuine improvement in the user experience.