![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&s=144)
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?v=4&s=144)
Commit activity
Last 12 weeks · 165 commits
Community health
2 of 6 standards met
50
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · 3 in progress · Last activity 4h ago
See all on GitHub →
Follow-up to @boris's review of #492 after #493 merged into that branch. Targets so the fix ships with #492 — that branch is where the junction is created (). Problem linked to the canonical copy with a bare relative target: POSIX symlinks resolve that against the link's own directory, so it works. Windows junctions are always absolute, and Node resolves a relative with — against , not the link's directory. Scaffolding from anywhere other than the project's parent therefore produced a junction pointing somewhere else entirely, and still succeeded, so nothing surfaced the problem: Claude Code just found no project skills. Simulating Node's junction handling with , cwd , project : Solution New exported computes the target from the link's own directory: Windows — resolves to an absolute path against , so the junction is correct regardless of the working directory. POSIX — stays relative, so a scaffolded project remains movable (copy or rename the directory and the symlink still resolves). The fallback to a plain copy (Windows without Developer Mode) is unchanged. Tests grows 3 cases (22 total, all passing): returns on POSIX. returns an absolute, link-relative path on — this is the regression guard; it fails against the pre-fix behavior (verified by reverting the platform branch locally: , 21 pass / 1 fail). run with set to an unrelated directory still produces a link whose target resolves to from the link's directory. Docs No change needed — the troubleshooting entry only says should link to , which is now true on Windows too. 🤖 Generated with Claude Code
Problem The CLI started three subprocesses after the scaffold step. These subprocesses also started when the dependency installation failed. Solution The CLI gets the template, the skills, and the commands from one tarball download. The CLI copies the skills to and makes links in . The CLI copies the commands to . The CLI does not start plugin subprocesses. It shows the install commands for the two optional plugins. The option adds only the agent files. If the download fails, the CLI stops. Git keeps the versions of the skills. The related documentation and skills show the new flow.
Recent fixes
What progressively register four storefront tools through the native API expose product search, product options, guest-cart reads, and an explicit add-to-cart capability document Chrome's testing flag, the Model Context Tool Inspector, Chrome DevTools MCP, and optional origin-trial setup Implementation notes keeps the WebMCP integration in one null-rendering Client Component with direct calls and cleanup validates tool arguments again in Server Actions and resolves exact, available, non-bundle variants before mutation keeps cart writes on the existing path, including BotID checks when enabled, and serializes browser cart writes returns reduced, bounded tool results without cart IDs, checkout URLs, payment data, customer data, or upstream error text reports ambiguous mutation outcomes as unsafe to retry WebMCP remains experimental, so unsupported browsers keep the normal storefront experience. Testing focused mocked checks for output budgets, exact option resolution, mutation serialization, redaction, and ambiguous outcomes native Chrome lifecycle smoke: four tools registered, abort cleanup removed them, remount registered them again without duplicates, and cleanup removed them again completed GraphQL codegen, then stopped because the required Shopify storefront environment variables are not available locally
Applies the vercel.com/design.md composition/restraint rules to the docs home page, preserving the installed Geistdocs/Geist foundation. Changes Remove the auto-scrolling logo marquee — design.md bans auto-scrolling marquees and decorative brand marks; the logos were decorative, not evidence. Tighten hero bottom padding ( → ) — the first viewport should carry evidence, not only a masthead; the reduced padding lifts the install prompt and first demo toward the fold. Kept intentionally The four feature rows — they are true peers, so the consistent rhythm is legitimate, not template noise. The centered hero, install toggle, and Geist tokens (the established foundation). Docs passes. Visual render verification not done (browser backend unavailable). 🤖 Generated with Claude Code
fix(docs): import the geistdocs stylesheet instead of copying its theme + migrate to new layoutMergedPR
Fixes the unstyled navbar dropdown / flyout menu. was a hand-copied snapshot of the geist theme rather than an import of the package's stylesheet. introduce new max-w- and text-heading- to match new vercel.com style
Structured data for AI agents
Repository: vercel/shop. Description: vercel/shop Stars: 45, Forks: 12. Primary language: TypeScript. Languages: TypeScript (80.4%), MDX (17.2%), JavaScript (1.6%), CSS (0.9%). License: MIT. Homepage: https://docs.vercel.shop Latest release: create-vercel-shop@0.3.1 (1mo ago). Open PRs: 3, open issues: 0. Last activity: 4h ago. Community health: 50%. Top contributors: laugharn, blurrah, christopherkindl, dancer, github-actions[bot], vercel[bot], molebox, gaojude.