░▒▓████████████████████████████████▓▒░ ░▒▓█ ▓▒░ ░▒▓█ ~ S W A M P ~ ▓▒░ ░▒▓█ ▓▒░ ░▒▓████████████████████████████████▓▒░
lon105.truehost.cloud
LOCATION:
/lib/node_modules/npm/node_modules/require-main-filename
☗ ROOT
↻ REFRESH
✎ CARVE FLESH
EDITING: README.md
# 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
CANCEL
Name
Type
Size
Modified
Actions
↩ ..
DIR
—
—
📄 CHANGELOG.md
MD
852 B
2021-03-10 14:36
EDIT
📄 index.js
JS
427 B
2021-03-10 14:36
EDIT
📄 LICENSE.txt
TXT
731 B
2021-03-10 14:36
EDIT
📄 package.json
JSON
1.7 KB
2021-03-10 14:36
EDIT
📄 README.md
MD
1 KB
2021-03-10 14:36
EDIT