HckApm/node_modules/detect-node-es
minicx 99e5f883a3 second commit 2023-12-23 14:56:27 +03:00
..
es5 second commit 2023-12-23 14:56:27 +03:00
esm second commit 2023-12-23 14:56:27 +03:00
LICENSE second commit 2023-12-23 14:56:27 +03:00
Readme.md second commit 2023-12-23 14:56:27 +03:00
package.json second commit 2023-12-23 14:56:27 +03:00

Readme.md

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.