Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 3.15.22.202
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
www /
unp-musonza /
node_modules /
detect-node /
Delete
Unzip
Name
Size
Permission
Date
Action
LICENSE
1.04
KB
-rw-r--r--
1985-10-26 08:15
Readme.md
691
B
-rw-r--r--
1985-10-26 08:15
browser.js
25
B
-rw-r--r--
1985-10-26 08:15
index.js
186
B
-rw-r--r--
1985-10-26 08:15
package.json
1.34
KB
-rw-r--r--
2021-02-04 21:24
Save
Rename
### Install ```shell npm install --save detect-node ``` ### Usage: ```js 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: ```js 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.