JSPM

is-node-process

1.1.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 8765093
  • Score
    100M100P100Q204517F
  • License MIT

Reliably determines if the code is running in Node.js

Package Exports

  • is-node-process
  • is-node-process/lib/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (is-node-process) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Package version

is-node-process

Reliably determines if the code is running in Node.js

Motivation

This library was created to provide a reliable way of determining a Node.js process, taking into account:

  • Browser-like environments (JSDOM);
  • Electron renderer process;
  • React Native runtime.

Why relying on window is a bad idea

There are environments (i.e. JSDOM) that polyfill the global window object and some of its API for the sake of emulating browser-like behaviors, while still remaining a Node.js process.

Why relying on process is a bad idea

Electron injects a global process object in the browser runtime when run with the nodeIntegration: true option.

Getting started

$ npm install is-node-process
# or
$ yarn add is-node-process
// any/code.js
const { isNodeProcess } = require('is-node-process')
isNodeProcess() // true/false