fix(plugins): keep bare installs on npm for launch

This commit is contained in:
Vincent Koc
2026-05-02 11:57:07 -07:00
parent a7a6d24147
commit cf21bcf9bf
14 changed files with 64 additions and 286 deletions

View File

@@ -15,8 +15,8 @@ combination.
You do not need to add your plugin to the OpenClaw repository. Publish to
[ClawHub](/tools/clawhub) and users install with
`openclaw plugins install <package-name>`. OpenClaw tries ClawHub first and
falls back to npm automatically for packages that still use npm distribution.
`openclaw plugins install clawhub:<package-name>`. Bare package specs still
install from npm during the launch cutover.
## Prerequisites
@@ -141,9 +141,8 @@ and provider plugins have dedicated guides linked above.
openclaw plugins install clawhub:@myorg/openclaw-my-plugin
```
OpenClaw also checks ClawHub before npm for bare package specs like
`@myorg/openclaw-my-plugin`; npm remains a fallback for packages that have
not migrated to ClawHub yet.
Bare package specs like `@myorg/openclaw-my-plugin` install from npm during
the launch cutover. Use `clawhub:` when you want ClawHub resolution.
**In-repo plugins:** place under the bundled plugin workspace tree — automatically discovered.