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: load source bundled plugins from pnpm workspaces

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-02 02:05:51 +01:00
parent 89f73a5ef2
commit 8d7f4d28ce
8 changed files with 69 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/plugins/building-plugins.md
View File

@@ -22,7 +22,9 @@ falls back to npm automatically for packages that still use npm distribution.
- Node >= 22 and a package manager (npm or pnpm)
- Familiarity with TypeScript (ESM)
- For in-repo plugins: repository cloned and `pnpm install` done
- For in-repo plugins: repository cloned and `pnpm install` done. Source
checkout plugin development is pnpm-only because OpenClaw loads bundled
plugins from the `extensions/*` workspace packages.
## What kind of plugin?

6
docs/plugins/dependency-resolution.md
View File

@@ -93,6 +93,12 @@ Bundled plugin manifests must not request dependency staging. Large or optional
plugin functionality should be packaged as a normal plugin and installed through
the same npm/git/ClawHub path as third-party plugins.
In source checkouts, OpenClaw treats the repository as a pnpm monorepo. After
`pnpm install`, bundled plugins load from `extensions/<id>` so package-local
workspace dependencies are available and edits are picked up directly. Source
checkout development is pnpm-only; plain `npm install` at the repository root is
not a supported way to prepare bundled plugin dependencies.
## Legacy cleanup
Older OpenClaw versions generated bundled-plugin dependency roots at startup or