claude-code - 💡(How to fix) Fix [DOCS] Cant configure plugin dependency from a different marketplace [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#50855Fetched 2026-04-20 12:11:11
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/plugin-dependencies#declare-a-dependency-with-a-version-constraint

Section/Topic

Plugin dependency

Current Documentation

"A different marketplace to resolve name in. Cross-marketplace dependencies are blocked unless the target marketplace is allowlisted in the root marketplace’s marketplace.json."

What's Wrong or Missing?

I am trying to configure a plugin dependency from another marketplace. The doc mention that The marketplace must be "allowlisted" in the marketplace.json file, but it does not specify how. If I add the depedency without this allowlist, the dependency is not loaded.

Suggested Improvement

Specify how to make this configuration. This is important in a multi marketplace environment.

Impact

High - Prevents users from using a feature

Additional Context

No response

extent analysis

TL;DR

To resolve the issue, you likely need to add the target marketplace to the "allowlist" in the marketplace.json file, but the exact configuration steps are missing from the documentation.

Guidance

  • Review the marketplace.json file format to understand how allowlists are typically configured, as the documentation for declaring a dependency with a version constraint might provide clues.
  • Look for any existing allowlist configurations in the marketplace.json file to determine the correct syntax and structure for adding a new marketplace.
  • Consider searching for examples or tutorials on configuring multi-marketplace environments, as these might provide insight into the missing configuration steps.
  • If possible, test adding the target marketplace to the allowlist using a trial-and-error approach, starting with a simple configuration and building upon it.

Example

No code example can be provided without more information on the marketplace.json file format and the expected allowlist configuration.

Notes

The provided documentation and issue description lack specific details on how to configure the allowlist, making it challenging to provide a precise solution. The guidance offered is based on the assumption that the marketplace.json file is where the allowlist configuration should be made, as hinted by the documentation.

Recommendation

Apply workaround: Since the exact configuration steps are not provided, attempting to find examples or trial-and-error approaches might be the most straightforward path forward until more detailed documentation is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING