JSPM – detect-node-es@1.1.0

Package Exports

detect-node-es
detect-node-es/es5/browser.js
detect-node-es/es5/node.js
detect-node-es/esm/browser.js
detect-node-es/esm/node.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 (detect-node-es) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

detect-node

This is a fork of detect-node.

Differences:

uses named export {isNode}
has d.ts integrated
supports ESM

Install

npm install --save detect-node-es

Usage:

-var isNode = require('detect-node');
+var {isNode} = require('detect-node-es');

if (isNode) {
  console.log("Running under Node.JS");
} else {
  alert("Hello from browser (or whatever not-a-node env)");
}

The check is performed as:

module.exports = false;

// Only Node.JS has a process variable that is of [[Class]] process
try {
 module.exports = Object.prototype.toString.call(global.process) === '[object process]' 
} catch(e) {}

Thanks to Ingvar Stepanyan for the initial idea. This check is both the most reliable I could find and it does not use process env directly, which would cause browserify to include it into the build.