vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 14:50:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(plugins): explain source-only package diagnostics (#77835) (#77842)

Browse Source
This commit is contained in:
hcl
2026-05-06 08:43:13 +08:00
committed by GitHub
parent bca6709203
commit d193d15f17
7 changed files with 19 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/channels/wechat.md
View File

@@ -149,6 +149,11 @@ openclaw plugins install "@tencent-weixin/openclaw-weixin" --force
openclaw gateway restart
```
If startup reports that the installed plugin package `requires compiled runtime
output for TypeScript entry`, the npm package was published without the compiled
JavaScript runtime files OpenClaw needs. Update/reinstall after the plugin
publisher ships a fixed package, or temporarily disable/uninstall the plugin.
Temporary disable:
```bash

6
docs/tools/plugin.md
View File

@@ -164,6 +164,12 @@ 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.
If a managed package warning says it `requires compiled runtime output for
TypeScript entry ...`, the package was published without the JavaScript files
OpenClaw needs at runtime. That is a plugin packaging issue, not a local config
problem. Update or reinstall the plugin after the publisher republishes compiled
JavaScript, or disable/uninstall that plugin until a fixed package is available.
Use `openclaw.runtimeExtensions` when published runtime files do not live at the
same paths as the source entries. When present, `runtimeExtensions` must contain
exactly one entry for every `extensions` entry. Mismatched lists fail install and