is-node

library1.1.1jsnpmunverified

This package provides a minimal utility to programmatically determine if the current JavaScript execution environment is Node.js. It achieves this by checking for the presence of the global `process` object and specific properties like `process.versions.node`. The current stable version is 1.1.1. The package maintains a relatively active release cadence, primarily for patch updates related to build processes (e.g., `npm ignore`). Its key differentiator is its singular focus and small footprint, offering a straightforward boolean value rather than a complex function or object. It's commonly employed in isomorphic libraries or application code that needs to adapt behavior between server-side Node.js and client-side browser environments.

npm install is-node

github ↗package ↗

INSTALL

IMPORT

SIG · IS-NODE

is-node

javascriptv1.1.1

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

isNode

✓ import isNode from 'is-node';

✗ import { isNode } from 'is-node';

The package exports a default boolean value (true if in Node.js, false otherwise), not a function or object. Use a default import for ESM.

isNode

✓ const isNode = require('is-node');

✗ const { isNode } = require('is-node');

For CommonJS, `require('is-node')` directly resolves to the exported boolean value.

isNode

✓ import isNode from 'is-node'; // In TypeScript, 'isNode' is directly typed as a boolean

The package ships with TypeScript types. The default export `isNode` is directly typed as a boolean, providing strong type inference.

Demonstrates how to import and use the `is-node` boolean to conditionally execute code, logging environment-specific details depending on whether the current runtime is Node.js.

import isNode from 'is-node'; function logEnvironmentDetails() { if (isNode) { console.log("Detected: Running in a Node.js environment."); // Node.js-specific global objects and APIs are available here console.log(`Node.js Version: ${process.version}`); console.log(`Current Working Directory: ${process.cwd()}`); // Example: process.stdout.write('Writing to stdout directly\n'); } else { console.log("Detected: Running in a non-Node.js environment (e.g., browser, Deno, Bun)."); // Browser-specific APIs would be available here (e.g., document, window) // console.log(`User Agent: ${navigator.userAgent}`); // document.getElementById('app').innerHTML = 'Hello from the browser!'; } } logEnvironmentDetails();

Debug

Known issues

gotchaThe `is-node` check relies on the global `process` object and specifically `process.versions.node`. While robust for typical Node.js environments, highly specialized or spoofed environments (e.g., some edge runtimes, custom JSDOM setups, or other JavaScript runtimes that partially emulate Node.js) might incorrectly report or fail to report as Node.js.

fix

For highly critical environment checks, consider more comprehensive or multi-factor detection strategies beyond `is-node` alone, or explicitly check for `process.versions.node` directly if that is the specific property your logic relies on.

affects: >=1.0.0

breakingPrior to version 1.1.0 (approximately, based on related package updates in the monorepo), the package might not have shipped TypeScript types directly. While not strictly a runtime breaking change, integrating older versions into TypeScript projects would require manual type declarations (`@types/is-node` or custom `d.ts`).

fix

Upgrade to `is-node@1.1.0` or later to leverage built-in TypeScript definitions and ensure proper type inference for the `isNode` boolean.

affects: <1.1.0

gotchaThis package is designed for a single purpose: detecting the Node.js runtime. It does not provide browser-specific feature detection or differentiate between various non-Node.js runtimes (e.g., Deno, Bun, Web Workers, Electron render process).

fix

If your application requires more granular environment detection (e.g., 'is in browser', 'is in Deno', 'is in Electron main/renderer'), use dedicated libraries or custom checks for those specific environments instead of relying solely on `is-node`.

affects: >=1.0.0

Errors

Common errors & fixes

TypeError: isNode is not a function

`is-node` exports a boolean value directly, not a callable function.

fix

Do not attempt to call `isNode`. Use it directly as a boolean condition, e.g., `if (isNode) { /* ... */ }`.

SyntaxError: Named export 'isNode' not found. The requested module 'is-node' does not provide an export named 'isNode'

Attempting to use a named import for `is-node`, which is a default export.

fix

Change the import statement to a default import: `import isNode from 'is-node';`.

ReferenceError: process is not defined

This error occurs if `is-node` is used in a non-Node.js environment where the global `process` object is entirely absent, and an upstream bundler or environment might not have correctly handled its Node.js-specific checks, or if other Node.js-specific code is executed assuming `process` is available.

fix

Ensure your build process correctly handles Node.js-specific code for different targets. If this error occurs in a browser environment, verify `is-node` itself is evaluating to `false` and that other Node.js assumptions are not present.

Upgrade

Version history

1.1.1latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

4 hits · last 30 days

node

Resources

githubhttps://github.com/MatthewSH/npm-packages ↗

packagehttps://www.npmjs.com/package/is-node ↗