Specify pnpm version in package.json#1
Merged
simonweniger merged 3 commits intomainfrom Apr 12, 2026
Merged
Conversation
Vercel was detecting pnpm-lock.yaml v9 as ambiguous between pnpm 9.x and 10.x and falling back to a project-creation-date heuristic. Pinning via the packageManager field makes Corepack/Vercel use a deterministic pnpm version and silences the warning.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pnpm 10 ignores dependency lifecycle scripts by default, which caused esbuild's postinstall (native binary setup) to be skipped and the subsequent vite build to fail. Allow-list esbuild via pnpm.onlyBuiltDependencies.
When Vercel builds the web package directly (without running the root 'pnpm -r build'), tsc could not resolve '@happy-shadows/core' because its dist/ outputs had never been emitted. Mark shadow-core as a composite project and add a TypeScript project reference from web. 'tsc -b' in web now builds shadow-core first, producing dist/index.js and dist/index.d.ts before type-checking web.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change pins the project to use pnpm version 10.20.0 by adding the
packageManagerfield to package.json.Summary
Added explicit package manager specification to ensure all developers and CI/CD environments use a consistent version of pnpm.
Key Changes
"packageManager": "pnpm@10.20.0"to package.jsonDetails
The
packageManagerfield is a standard npm feature that enforces a specific package manager version. This ensures reproducible builds and prevents compatibility issues that may arise from different pnpm versions being used across the team.https://claude.ai/code/session_012xBSdrYYDiksEEEMbaepJQ