Pin pnpm 10.25.0 and Node 20.x in package.json - #1906
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
marcleblanc2
enabled auto-merge (squash)
September 11, 2026 08:02
Vercel picked pnpm 9 "based on project creation date" while .tool-versions says pnpm 10.25.0. packageManager and engines make the build use the same toolchain as local development. Amp-Thread-ID: https://ampcode.com/threads/T-01a08e2d-682f-75dd-a050-cb9bf8888dac Co-authored-by: Amp <amp@ampcode.com>
marcleblanc2
force-pushed
the
build/pin-toolchain
branch
from
September 11, 2026 08:02
19eafac to
da820be
Compare
Contributor
|
Why not upgrade these to node 24 and pnpm 12? |
valerybugakov
approved these changes
Sep 11, 2026
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
3 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.
Vercel's build log says
Using pnpm@9.x based on project creation date, while.tool-versionspins pnpm 10.25.0 and Node 20.19.6. AddingpackageManagerandenginesmakes Vercel (and Corepack) use the same versions as local development.Verified locally with pnpm 10.25.0 / Node 20.19.6:
pnpm install --frozen-lockfileandpnpm buildboth succeed. pnpm 10 skips dependency postinstall scripts by default (it lists contentlayer, esbuild, protobufjs, unrs-resolver as ignored); the build does not need any of them.Watch the Vercel preview build log on this PR for
Using pnpm@10.Part of the Vercel audit in #1905 (task 3).