> ## Documentation Index
> Fetch the complete documentation index at: https://autclaw.shop/llms.txt
> Use this file to discover all available pages before exploring further.
# JavaScript tools, Cron, and groups
> Use importModule, importJs, system utilities, Cron scheduled tasks, and group management methods in JavaScript plugins.
This page covers `middleware.js` utility functions, cross-file references, runtime scheduled commands, and group management methods. Public plugins should prefer the explicitly listed functions and avoid relying on unpublished internal actions.
## `importModule(module, versionOrOptions?, manager?)`
Ensure an npm dependency is available, then return the result of `require(module)`.
Module name used by `require(...)`.
A string means version. An object can contain `package`, `version`, and `manager`.
Real package name. Use this when the package name differs from the import name, such as subpath imports or aliased packages.
Required version.
Package manager name. Usually you do not need to pass this; the runtime handles it by default.
```js theme={null}
const { importModule } = require('./middleware.js')
const dayjs = await importModule('dayjs')
const lodash = await importModule('lodash', '4.17.21')
const axios = await importModule('axios', {
package: 'axios',
version: '1.7.9',
manager: 'npm',
})
```
Prefer declaring fixed dependencies in manifest `dependency`. `importModule(...)` is useful for on-demand loading or compatibility with older plugins.
## `importJs(target)`
`importJs(...)` is a global function in the ES5 / JavaScript runtime. It references other `.js` files in the plugin workspace, or files from another plugin in the same JavaScript runtime family. It eventually returns `module.exports` from the target file, similar to `require(resolvedPath)`.
```js theme={null}
// Reference hook.js in the current plugin workspace.
const hook = importJs('hook')
// Reference hook.js from another plugin.
const marketHook = importJs('specter:hook.js')
```
### `target` format
| Syntax | Meaning |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| `importJs('hook')` | Look up `hook.js` in the current runtime workspace. Adds `.js` automatically when no extension exists. |
| `importJs('lib/tool.js')` | Look up `lib/tool.js` in the current runtime workspace. |
| `importJs('specter:hook.js')` | Cross-plugin reference: text before the colon is the target plugin namespace, text after the colon is the file path inside the target plugin. |
| `require('specter:hook.js')` | Node.js / JavaScript runtime also normalizes this scoped request to the target file in the workspace. |
`source_script_id` / namespace matching rules:
* The `specter` before the colon is not a folder name. The runtime matches it against the target plugin author, plugin name, marketplace author, plugin ID prefix, and marketplace source script ID (`source_script_id`) prefix.
* For marketplace plugins, `source_script_id` usually looks like `specter:hook`. The runtime uses the prefix before the colon, so `importJs('specter:hook.js')` can locate that source plugin.
* If both a marketplace plugin and a local plugin match the same namespace, the marketplace plugin wins. If no marketplace match exists, local plugins are considered.
### File resolution behavior
* The path after the colon is the file path inside the target plugin. For example, `specter:lib/hook` resolves to `lib/hook.js` in the target plugin.
* `.js` is added automatically when no extension exists.
* The target file is copied into the current runtime workspace, and the runtime only loads from the workspace.
* Escaping the workspace is prohibited. For example, if resolution lands outside the workspace, it reports `importJs target is outside runtime workspace`.
* A missing target reports `importJs target not found`. If no cross-plugin namespace match exists, the runtime continues as a normal current-workspace file lookup and then reports not found if still missing.
* Only the same runtime family can reference each other: `es5` can only reference `es5`; `nodejs` / `typescript` can reference each other; they cannot cross to Python or other runtimes.
* If the namespace matches a plugin but the runtime family is incompatible, it reports runtime mismatch directly instead of falling back to mixed use.
`importJs(...)` is for reusing common helpers. Do not use it to read user data, logs, databases, or secret files. Do not rely on the internal file structure of unpublished plugins.
## System and utility functions
| Function | Purpose | Parameters | Returns |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------- | ------------------------------ |
| `render(template, selector, data)` | Render HTML / template, often to generate images. The current runtime may return an empty result depending on deployment capability. | `template`: template code; `selector`: selector; `data`: template data. | `Promise` |
| `getActiveImtypes()` | Get enabled IM types. | None | `Promise` |
| `name()` | Get bot name. | None | `Promise` |
| `domain()` | Get local runtime domain, usually `http://127.0.0.1:`. | None | `Promise` |
| `port()` | Get autClaw service port. | None | `Promise` |
| `machineId()` | Get machine ID. | None | `Promise` |
| `version()` | Get autClaw version. | None | `Promise` |
| `versionInfo()` | Get structured version information. | None | `Promise