Node.js Runtime for Windows x64

24.15.0 · active · verified Sun Apr 19

This package provides a specific, pre-compiled Node.js runtime binary for Windows 64-bit systems. It allows developers to bundle a particular Node.js version as a project dependency, ensuring consistent execution environments without requiring a system-wide Node.js installation or relying on version managers. The package tracks various Node.js releases, with the version number (e.g., 24.15.0) directly corresponding to the Node.js version it contains. New major versions typically align with the official Node.js release schedule (April and October). This package is particularly useful for projects requiring strict control over their Node.js runtime, for CI/CD pipelines, or in environments where global Node.js installations are undesirable or restricted. It aims to provide a reliable, isolated Node.js environment within a project's `node_modules` directory.

Common errors

```
Error: Command failed with ENOENT: node --version
```
cause The `node` command could not be found in the system's PATH, likely because the package was not installed or the environment variable is not correctly configured for direct terminal use.

fix If running inside an npm script, ensure `node-win-x64` is listed in `devDependencies` or `dependencies` in `package.json` and `npm install` has been run. If running directly in the terminal, use `npx node-win-x64 --version` or ensure your system's PATH includes the directory where the Node.js executable is located if you intend to use a global installation.
```
npm should be run outside of the node repl, in your normal shell.
```
cause Attempting to execute `npm` commands directly within the Node.js interactive interpreter (REPL) launched via `node.exe`.

fix Exit the Node.js REPL (by pressing Ctrl+C twice or typing `.exit`) and run `npm` commands directly in your command prompt or PowerShell terminal. `npm` is a separate command-line tool, not an internal Node.js command.

Warnings

gotcha Installing `node-win-x64` as a local dependency means `npm` scripts will use this bundled Node.js version. However, global `node` or `npm` commands executed directly in the terminal (outside of `npm run` scripts) will still use your system's globally installed Node.js.
Fix: Be explicit about which Node.js executable you are running. Use `npm run` for project-specific Node.js, or `npx node-win-x64` for direct execution of the bundled binary. Consider using `nvm-windows` for managing global Node.js versions if you need to frequently switch between them for system-wide commands.
breaking This package provides a specific Node.js version. If your project relies on features or APIs introduced in newer Node.js versions, or deprecated in older ones, ensure the `node-win-x64` version matches your requirements. Upgrading this package effectively upgrades your project's Node.js runtime.
Fix: Always pin the exact version of `node-win-x64` in `package.json` to ensure deterministic builds. Regularly review Node.js release notes for breaking changes when updating the package version. Use `npm install node-win-x64@<version>` to specify.
gotcha When using `node-win-x64`, ensure that any native Node.js modules (C++ add-ons) in your project are compiled against the specific Node.js version bundled in this package. Mismatched Node.js and native module binaries can lead to runtime errors.
Fix: Use `node-gyp rebuild` with the correct Node.js version in PATH if you are building native modules. Often, if `node-win-x64` is used in `npm` scripts, `node-gyp` will automatically pick up the local Node.js version. Ensure necessary build tools (like Visual Studio on Windows) are available if you are compiling native modules.

Install

npm install node-win-x64 npm
yarn add node-win-x64 yarn
pnpm add node-win-x64 pnpm

Imports

Node.js executable path
wrong:
```
import { node } from 'node-win-x64';
```
correct:
```
const { resolve } = require('path');
const nodeExecutable = resolve(__dirname, 'node_modules', 'node-win-x64', 'bin', 'node.exe');
```
This package provides a binary, not a JavaScript module. Access the Node.js executable directly from the `bin` directory within the installed package. The exact path may vary slightly by OS but typically includes `node.exe` on Windows.
npm-provided 'node' command
wrong:
```
import node from 'node-win-x64/node';
```
correct:
```
npm install node-win-x64
# Then, in package.json scripts:
"scripts": {
  "start": "node script.js"
}
```
When `node-win-x64` is installed as a dependency, `npm` (and `yarn`, `pnpm`) automatically add the `node_modules/.bin` directory to the PATH when running scripts. This means `node` in `package.json` scripts will resolve to the locally bundled binary.
npx command
wrong:
```
npx node --version
```
correct:
```
npx node-win-x64 --version
# or to run a script:
npx node-win-x64 script.js
```
The `npx` command can directly execute the Node.js binary provided by the `node-win-x64` package without needing to specify its full path. This is useful for one-off commands or testing specific Node.js versions.

Quickstart

Demonstrates how to install `node-win-x64` and use the bundled Node.js executable for project scripts via `package.json`.

{
  "name": "my-project",
  "version": "1.0.0",
  "scripts": {
    "check-node-version": "node --version",
    "run-script": "node my-script.js"
  },
  "dependencies": {
    "node-win-x64": "24.15.0"
  }
}

// my-script.js
console.log('Hello from Node.js bundled by node-win-x64!');
console.log(`Node.js version: ${process.version}`);
console.log(`Platform: ${process.platform}`);
console.log(`Architecture: ${process.arch}`);

// To run:
// npm install
// npm run check-node-version
// npm run run-script

view raw JSON →