nextjs - 💡(How to fix) Fix Unable to install Claude 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#88467Fetched 2026-04-08 02:04:46
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Error Message

Current behaviour: Error: Failed to install: Source path does not exist /Users/user/.claude/plugins/marketplaces/nextjs/plugins/cache-components

Root Cause

The issue is because the claude plugin actually lives at /Users/user/.claude/plugins/marketplaces/nextjs/.claude-plugins/plugins/cache-components

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.6.0: Mon Aug 11 21:16:31 PDT 2025; root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12
Binaries:
  Node: 24.10.0
  npm: 11.6.1
  Yarn: 1.22.22
  pnpm: 10.22.0
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: standalone
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/vercel/next.js/blob/canary/.claude-plugin/marketplace.json

To Reproduce

  1. Follow instructions here: https://github.com/vercel/next.js/tree/canary/.claude-plugin/plugins
  2. Run /plugin install cache-components@nextjs

Current vs. Expected behavior

Current behaviour: Error: Failed to install: Source path does not exist /Users/user/.claude/plugins/marketplaces/nextjs/plugins/cache-components

Expected behaviour: success

The issue is because the claude plugin actually lives at /Users/user/.claude/plugins/marketplaces/nextjs/.claude-plugins/plugins/cache-components

Perhaps this is because it https://github.com/vercel/next.js/blob/canary/.claude-plugin/marketplace.json defines the src directory incorrectly.

Two solutions:

  1. update marketplace.json to include .claude-plugins in path
  2. or; move plugins/ to root directory

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.6.0: Mon Aug 11 21:16:31 PDT 2025; root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12
Binaries:
  Node: 24.10.0
  npm: 11.6.1
  Yarn: 1.22.22
  pnpm: 10.22.0
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: standalone

Which area(s) are affected? (Select all that apply)

Instrumentation

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

extent analysis

TL;DR

Update the marketplace.json file to include the correct path to the plugins directory, likely by adding .claude-plugins to the src directory path.

Guidance

  • Verify the current path in marketplace.json and compare it to the actual location of the plugins directory, which is /Users/user/.claude/plugins/marketplaces/nextjs/.claude-plugins/plugins/cache-components.
  • Update the marketplace.json file to reflect the correct path, using one of the two suggested solutions: either update the src directory to include .claude-plugins or move the plugins directory to the root directory.
  • After making the change, re-run the /plugin install cache-components@nextjs command to test if the issue is resolved.
  • If the issue persists, double-check the file system and configuration for any other discrepancies in path names or locations.

Example

No code snippet is provided as the issue is related to configuration and file paths.

Notes

The solution assumes that the issue is indeed caused by the incorrect path in marketplace.json. If the problem persists after applying the suggested fix, further investigation into the plugin installation process and the next.js configuration may be necessary.

Recommendation

Apply the workaround by updating the marketplace.json file to include the correct path to the plugins directory, as this is a direct fix for the identified issue.

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

nextjs - 💡(How to fix) Fix Unable to install Claude Plugin [1 comments, 2 participants]