nextjs - 💡(How to fix) Fix Fix .claude-plugin/marketplace.json source path for cache-components plugin [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
vercel/next.js#92739Fetched 2026-04-15 06:18:40
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
closed ×1commented ×1labeled ×1locked ×1

Error Message

Error:

Fix Action

Fix

Either:

Option A — Update the source path in the manifest to include the .claude-plugin/ prefix:

{
  "source": "./.claude-plugin/plugins/cache-components"
}

Option B — Move the plugin directory to the repo root:

plugins/cache-components/   ← move here from .claude-plugin/plugins/cache-components/

Option B matches the convention used by other marketplace repos (e.g. anthropics/claude-code keeps plugins at plugins/ in the repo root).

Code Example

{
  "source": "./plugins/cache-components"
}

---

.claude-plugin/plugins/cache-components/

---

{
  "source": "./.claude-plugin/plugins/cache-components"
}

---

plugins/cache-components/   ← move here from .claude-plugin/plugins/cache-components/

---

npx claudepluginhub vercel/next.js --plugin cache-components --yes --scope project

---

Failed to install plugin "cache-components@nextjs":
  Source path does not exist: ~/.claude/plugins/marketplaces/nextjs/plugins/cache-components
RAW_BUFFERClick to expand / collapse

Bug

The source path in .claude-plugin/marketplace.json is incorrect, causing plugin installation to fail.

Current manifest (.claude-plugin/marketplace.json):

{
  "source": "./plugins/cache-components"
}

Actual plugin location:

.claude-plugin/plugins/cache-components/

Source paths in marketplace.json are resolved relative to the repository root. The current path ./plugins/cache-components resolves to plugins/cache-components/ at the repo root, which does not exist. The plugin files are actually nested inside .claude-plugin/plugins/cache-components/.

Fix

Either:

Option A — Update the source path in the manifest to include the .claude-plugin/ prefix:

{
  "source": "./.claude-plugin/plugins/cache-components"
}

Option B — Move the plugin directory to the repo root:

plugins/cache-components/   ← move here from .claude-plugin/plugins/cache-components/

Option B matches the convention used by other marketplace repos (e.g. anthropics/claude-code keeps plugins at plugins/ in the repo root).

Steps to reproduce

npx claudepluginhub vercel/next.js --plugin cache-components --yes --scope project

Error:

✘ Failed to install plugin "cache-components@nextjs":
  Source path does not exist: ~/.claude/plugins/marketplaces/nextjs/plugins/cache-components

extent analysis

TL;DR

Update the source path in .claude-plugin/marketplace.json to include the correct relative path to the plugin directory.

Guidance

  • Verify the actual location of the plugin files and update the source path in marketplace.json accordingly.
  • Consider moving the plugin directory to the repository root to match the convention used by other marketplace repositories.
  • Check the error message for the exact path that is being resolved incorrectly.
  • Test the updated marketplace.json file by running the npx claudepluginhub command again.

Example

{
  "source": "./.claude-plugin/plugins/cache-components"
}

Notes

The fix assumes that the plugin files are indeed located in the .claude-plugin/plugins/cache-components/ directory. If the files are located elsewhere, the source path should be updated accordingly.

Recommendation

Apply workaround by updating the source path in marketplace.json to include the correct relative path to the plugin directory, as this is a more straightforward solution than moving the plugin directory to the repository root.

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