@leeovery/claude-manager 2.0.3 → 2.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +12 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -57,6 +57,16 @@ The manager will:
|
|
|
57
57
|
|
|
58
58
|
That's it. Future `npm install` and `npm update` runs will automatically sync all plugins.
|
|
59
59
|
|
|
60
|
+
### pnpm
|
|
61
|
+
|
|
62
|
+
pnpm requires claude-manager as a direct dependency (it doesn't expose binaries from transitive dependencies):
|
|
63
|
+
|
|
64
|
+
```bash
|
|
65
|
+
pnpm add @leeovery/claude-manager @your-org/claude-your-plugin
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
pnpm also blocks postinstall scripts by default. After installing, run `pnpm approve-builds` to approve the packages, then `pnpm install` again.
|
|
69
|
+
|
|
60
70
|
## How It Works
|
|
61
71
|
|
|
62
72
|
1. Plugin packages have `@leeovery/claude-manager` as a dependency
|
|
@@ -98,6 +108,8 @@ The manager provides a CLI tool for managing plugins:
|
|
|
98
108
|
| `npx claude-plugins add <package>` | Manually add a plugin |
|
|
99
109
|
| `npx claude-plugins remove <package>` | Remove a plugin and its assets |
|
|
100
110
|
|
|
111
|
+
For pnpm users, use `pnpm exec claude-plugins` instead of `npx claude-plugins`.
|
|
112
|
+
|
|
101
113
|
## Creating Plugins
|
|
102
114
|
|
|
103
115
|
Want to create your own skill or command packages?
|