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

docs(plugins): clarify clawhub npm migration

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-29 06:09:27 +01:00
parent 8d78451e8b
commit 2b0b614417
20 changed files with 145 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/plugins/sdk-setup.md
View File

@@ -477,7 +477,7 @@ The `ChannelSetupWizard` type supports `credentials`, `textInputs`, `dmPolicy`,
## Publishing and installing
**External plugins:** publish to [ClawHub](/tools/clawhub) or npm, then install:
**External plugins:** publish to [ClawHub](/tools/clawhub), then install:
<Tabs>
<Tab title="Auto (ClawHub then npm)">
@@ -494,10 +494,11 @@ The `ChannelSetupWizard` type supports `credentials`, `textInputs`, `dmPolicy`,
```
</Tab>
<Tab title="npm package spec">
There is no matching `npm:` override. Use the normal npm package spec when you want the npm path after ClawHub fallback:
Use npm when a package has not moved to ClawHub yet, or when you need a
direct npm install path during migration:
```bash
openclaw plugins install @myorg/openclaw-my-plugin
openclaw plugins install npm:@myorg/openclaw-my-plugin
```
</Tab>