chore(deps): pin node 24 via engines - #255
Closed
ganymedio wants to merge 1 commit into
Closed
Conversation
Add engines.node 24.x so Vercel builds and runs the site on Node 24 regardless of the Project Settings value; Node 20 is disabled on Vercel from 2026-10-01. packageManager (pnpm@10.33.0) and the 14-day minimum-release-age cooldown in .npmrc were already in place and are unchanged.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Superseded by #256, which carries both commits and targets |
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.
What changes
package.json: add"engines": { "node": "24.x" }.Why
Vercel reads
engines.nodeto select the build and runtime Node version, overriding the Project Settings value. Node 20 is disabled on Vercel from 2026-10-01, so pinning 24.x here makes the deployed Node version explicit and version-controlled.packageManageris alreadypnpm@10.33.0and.npmrcalready enforcesminimum-release-age=20160(14-day install cooldown); both are unchanged.Verification
pnpm install --frozen-lockfile: succeeds, lockfile unchanged. pnpm 10 reportsIgnored build scripts: @tailwindcss/oxide@4.1.11; the build does not need that script, so noonlyBuiltDependenciesentry was added.pnpm build(next build): succeeds, full route table emitted.