Inicio Explorar Axuda
Iniciar sesión
ver2ex
/
hw-react-1
Seguir 1
Destacar 0
Fork 0
Ficheiros Incidencias 1 Pull Requests 0 Wiki
Árbore: 2389e7160b
Ramas Etiquetas
hw-react-1
/
node_modules
/
detect-node
Irina Glushko 2389e7160b HW1 done %!s(int64=3) %!d(string=hai) anos
..
LICENSE 2389e7160b HW1 done %!s(int64=3) %!d(string=hai) anos
Readme.md 2389e7160b HW1 done %!s(int64=3) %!d(string=hai) anos
browser.js 2389e7160b HW1 done %!s(int64=3) %!d(string=hai) anos
index.esm.js 2389e7160b HW1 done %!s(int64=3) %!d(string=hai) anos
index.js 2389e7160b HW1 done %!s(int64=3) %!d(string=hai) anos
package.json 2389e7160b HW1 done %!s(int64=3) %!d(string=hai) anos

Readme.md

Install

npm install --save detect-node

Usage:

var isNode = require('detect-node');

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.