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

fix(plugins): require declared runtime setup entries

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-01 22:36:08 +01:00
parent c2a2cfe314
commit d2ae2a3fb0
6 changed files with 140 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/plugins/sdk-entrypoints.md
View File

@@ -28,9 +28,12 @@ JavaScript when available:
`extensions` and `setupEntry` remain valid source entries for workspace and git
checkout development. `runtimeExtensions` and `runtimeSetupEntry` are preferred
when OpenClaw loads an installed package and let npm packages avoid runtime
TypeScript compilation. If an installed package only declares a TypeScript
source entry, OpenClaw will use a matching built `dist/*.js` peer when one
exists, then fall back to the TypeScript source.
TypeScript compilation. Explicit runtime entries are required: `runtimeSetupEntry`
requires `setupEntry`, and missing `runtimeExtensions` or `runtimeSetupEntry`
artifacts fail install/discovery instead of silently falling back to source. If
an installed package only declares a TypeScript source entry, OpenClaw will use a
matching built `dist/*.js` peer when one exists, then fall back to the TypeScript
source.
All entry paths must stay inside the plugin package directory. Runtime entries
and inferred built JavaScript peers do not make an escaping `extensions` or