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
42 lines
1.0 KiB
Markdown
42 lines
1.0 KiB
Markdown
# get-caller-file
|
|
|
|
[](https://travis-ci.org/stefanpenner/get-caller-file)
|
|
[](https://ci.appveyor.com/project/embercli/get-caller-file/branch/master)
|
|
|
|
This is a utility, which allows a function to figure out from which file it was invoked. It does so by inspecting v8's stack trace at the time it is invoked.
|
|
|
|
Inspired by http://stackoverflow.com/questions/13227489
|
|
|
|
*note: this relies on Node/V8 specific APIs, as such other runtimes may not work*
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
yarn add get-caller-file
|
|
```
|
|
|
|
## Usage
|
|
|
|
Given:
|
|
|
|
```js
|
|
// ./foo.js
|
|
const getCallerFile = require('get-caller-file');
|
|
|
|
module.exports = function() {
|
|
return getCallerFile(); // figures out who called it
|
|
};
|
|
```
|
|
|
|
```js
|
|
// index.js
|
|
const foo = require('./foo');
|
|
|
|
foo() // => /full/path/to/this/file/index.js
|
|
```
|
|
|
|
|
|
## Options:
|
|
|
|
* `getCallerFile(position = 2)`: where position is stack frame whos fileName we want.
|