875c7f9b91
- Add full Telegram bot functionality with Z.AI API integration
- Implement 4 tools: Bash, FileEdit, WebSearch, Git
- Add 3 agents: Code Reviewer, Architect, DevOps Engineer
- Add 6 skills for common coding tasks
- Add systemd service file for 24/7 operation
- Add nginx configuration for HTTPS webhook
- Add comprehensive documentation
- Implement WebSocket server for real-time updates
- Add logging system with Winston
- Add environment validation
🤖 zCode CLI X - Agentic coder with Z.AI + Telegram integration
27 lines
1.0 KiB
Markdown
27 lines
1.0 KiB
Markdown
# 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
|