Repository navigation
build: pin the vercel build to node 24 - #156
Merged
Merged
Conversation
- vercel stops building projects on node 20 on 2026-10-01 and this project still deploys on node 20 - engines in package.json overrides the node version in the vercel project settings, so previews, staging and production each pick it up from their branch
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
Description
enginespin overrides the Node version in the Vercel project settings, so the preview on this PR builds on Node 24 before anything mergesTesting
Node.js Version "24.x" will be used instead, and the e2e suite run against the preview gives the same result as Node 20 production, 67 passed and 1 skipped