Support maintaining ClaudeCode plugin dependencies #42974
Replies: 2 comments 2 replies
New package manager questionnaireDid you read our documentation on adding a package manager?
BasicsWhat's the name of the package manager?Claude Code What language(s) does this package manager support?Claude Plugins How popular is this package manager?ClaudeCode is very popular Does this language have other (competing?) package managers?
What are the big selling points for this package manager?N/A Detecting package filesWhat kind of package files, and names, does this package manager use?Which
|
|
This sounds reasonable - but to confirm, are these plugins that are distributed i.e. on GitHub? Got any examples we can take a look at? |
Uh oh!
There was an error while loading. Please reload this page.
Tell us more.
In a recent version ClaudeCode (
v2.1.110) added the possibility define Claude plugins as dependencies of other plugins.https://code.claude.com/docs/en/plugin-dependencies
For version parsing the
semvernpm package internally, so using thenpmversioning seems like an obvious choice.The problem mostly arises we have to resolve the external marketplaces which are defined on a repo, user space, machine or remote level configured. To capture most we most likely would have to run
claudeitself to get the full list of marketplaces (plugin marketplace list) and their locationWith that information we can use the the existing datasources to fetch the available versions.
There are no lockfiles
All reactions