openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@59c523c6b5

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-05-03 15:52:19 +00:00
parent 98d36c4e1e
commit 0d36732621
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "e2c8db2cad406b00e37a2b60e7767ad6232fbf3a",
"syncedAt": "2026-05-03T15:25:51.054Z"
"sha": "59c523c6b530224f55a5c00baca761563a180e4a",
"syncedAt": "2026-05-03T15:50:12.340Z"
}

3
docs/tools/plugin.md
View File

@ -161,6 +161,9 @@ Native plugin npm packages must declare `openclaw.extensions` in `package.json`.
Each entry must stay inside the package directory and resolve to a readable
runtime file, or to a TypeScript source file with an inferred built JavaScript
peer such as `src/index.ts` to `dist/index.js`.
Packaged installs must ship that JavaScript runtime output. The TypeScript
source fallback is for source checkouts and local development paths, not for
npm packages installed into OpenClaw's managed plugin root.
Use `openclaw.runtimeExtensions` when published runtime files do not live at the
same paths as the source entries. When present, `runtimeExtensions` must contain