mirror of
https://github.com/actions/setup-python.git
synced 2025-06-14 08:17:12 +02:00
Initial pass
This commit is contained in:
26
node_modules/require-main-filename/README.md
generated
vendored
Normal file
26
node_modules/require-main-filename/README.md
generated
vendored
Normal file
@ -0,0 +1,26 @@
|
||||
# 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
|
Reference in New Issue
Block a user