Repository navigation
Conversation
- Add .node-version (24.22.1) as the single source of truth; fnm reads it locally and CI reads it via setup-node's node-version-file. - Set engines.node to 24.x so Vercel builds and functions run on 24. - Align @types/node to ^24 so types match the runtime and can't expose Node 26-only APIs that would fail on 24 at runtime. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
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
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
Runs the project on Node.js 24 LTS (24.22.1) everywhere: locally, in CI, and in Vercel builds and functions.
Why
Local development already ran on Node 24 through fnm, but CI and the Vercel project were still on 22.x. Vercel deprecates Node 20 on 2026-10-01, and 24 is now its default LTS. Using one runtime everywhere means CI and production behave like local.
Changes
.node-version(new): pins24.22.1. fnm reads it locally, and CI reads it throughsetup-node'snode-version-file.package.json: changesengines.nodefrom>=20.19.0to24.x. Vercel reads this when it builds and runs functions..github/workflows/ci.yml: both jobs (checkande2e) get their Node version from.node-versioninstead of hard-coding22.x.@types/node: moves from^26.3.0to^24.19.2so the types match the runtime. On 26, code could use Node 26-only APIs that pass the type check and then crash on 24.json-formatter's Node.js version from22.xto24.xin the dashboard, so it agrees withengines. That change is not part of this diff.Verified on Node 24.22.1:
pnpm checkpasses (545 unit tests, 0 errors) and so doespnpm test:e2e(25 passed, 2 skipped). Afterpnpm dedupethe lockfile still has a single@codemirror/state.🤖 Generated with Claude Code