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 /
wb /
node_modules /
require-main-filename /
Delete
Unzip
Name
Size
Permission
Date
Action
.npmignore
35
B
-rw-rw-r--
2022-08-30 11:49
.travis.yml
84
B
-rw-rw-r--
2022-08-30 11:49
LICENSE.txt
731
B
-rw-rw-r--
2022-08-30 11:49
README.md
1.04
KB
-rw-rw-r--
2022-08-30 11:49
index.js
427
B
-rw-rw-r--
2022-08-30 11:49
package.json
750
B
-rw-rw-r--
2022-08-30 11:49
test.js
1.03
KB
-rw-rw-r--
2022-08-30 11:49
Save
Rename
# require-main-filename [](https://travis-ci.org/yargs/require-main-filename) [](https://coveralls.io/r/yargs/require-main-filename?branch=master) [](https://www.npmjs.com/package/require-main-filename) `require.main.filename` is great for figuring out the entry point for the current application. This can be combined with a module like [pkg-conf](https://www.npmjs.com/package/pkg-conf) to, _as if by magic_, load top-level configuration. Unfortunately, `require.main.filename` sometimes fails when an application is executed with an alternative process manager, e.g., [iisnode](https://github.com/tjanczuk/iisnode). `require-main-filename` is a shim that addresses this problem. ## Usage ```js var main = require('require-main-filename')() // use main as an alternative to require.main.filename. ``` ## License ISC