Repository navigation
Fix the Vercel build: run the pinned pnpm through npx - #7
Conversation
Vercel's bundled pnpm reads packageManager (pnpm@12.11.2), tries to switch itself to it, and fails with "the installed pnpm wrapper is missing". site/vercel.json now runs pnpm 12.11.2 through npx for both install and build, so Vercel's own pnpm is never used. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Pin Vercel commands to pnpm 12.11.2 site/vercel.json, docs/releasing.md |
The install and build commands use pnpm 12.11.2 through npx. The install command retains the frozen lockfile and echo-site filter. The release instructions point to the Vercel configuration and state that its pinned version should match packageManager in package.json. |
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Bug fix
Merge Risk: 
3c331
-
The Vercel configuration and release instructions are aligned, with no identified merge-blocking risk.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly and concisely describes the main change: running the pinned pnpm version through npx for the Vercel build. Description check The description explains what changed, why it was needed, and how it was tested. It covers the required sections with sufficient detail, although it does not reproduce the template checklist. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
The first Vercel deployment failed during install:
Vercel's bundled pnpm reads
packageManager(pnpm@12.11.2) and tries to switch itself to that version, which fails.site/vercel.jsonnow runs pnpm 12.11.2 throughnpxfor both install and build, so Vercel's own pnpm is never used.docs/releasing.mdnotes why and says to keep the version in step withpackageManager.Verified locally by simulating the Vercel build from a fresh clone:
npx pnpm@12.11.2 install --frozen-lockfile --filter echo-siteandVERCEL=1 npx pnpm@12.11.2 run buildfromsite/both succeed, and the build includes the Vercel Analytics script. This PR's Vercel preview deployment confirms it on Vercel itself.🤖 Generated with Claude Code
Summary by CodeRabbit