Repository navigation
presets(vercel): support node.js 26 - #4969
Merged
Merged
Conversation
The preset hard-coded Node.js 22 and 24, so a Node 26 build (or `engines.node: 26.x`) deployed on nodejs24.x. Derive the supported versions from the even majors from 22 up to the newest known one or the build's own major, so future even versions need no change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 of 8 tasks
|
@ali-vercel is attempting to deploy a commit to the Nitro Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
|
Caution Review failedThe pull request is closed.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Vercel supports every Node.js major from 26 onwards, not only even ones, so a Node.js 27 build or `engines.node: 27.x` should deploy on `nodejs27.x`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ali-vercel
changed the title
Vercel lists each supported major explicitly (build-utils NODE_VERSIONS). Newer builds clamp to 26 instead of emitting a runtime Vercel does not offer yet.
pi0x
changed the title
Contributor
|
I changed this to a fixed list of Triaged with AI assistance. |
pi0
marked this pull request as ready for review
November 1, 2026 04:08
pi0
approved these changes
Nov 1, 2026
pi0
changed the title
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.
🔗 Linked issue
None filed; context below. Happy to open an issue first if you'd prefer to discuss it there.
❓ Type of change
📚 Description
Summary: Let the
vercelpreset resolve Node.js 26 as the function runtime, instead of falling back tonodejs24.x.Context: Vercel made Node.js 26 generally available on 2026-10-29. New projects default to
26.x, and projects with an openengines.noderange such as>=22now build on Node.js 26. The preset only knows[22, 24], so a Node.js 26 build quietly deploysnodejs24.x. Withengines.node: "26.x"it warns that only 22 and 24 are supported, then deploysnodejs24.xanyway.The supported list is now
[22, 24, 26], matchingNODE_VERSIONSin Vercel'sbuild-utils. A build on 23 or 25 uses the next supported version, and a build on a newer major usesnodejs26.xuntil Vercel adds it. Node.js 20 stays out, as #4768 intended. An explicitvercel.functions.runtimestill takes precedence, andnodejs26.xis added to its type.Vercel only lists Node.js 22, 24 and 26 today (no public source says newer majors will be added automatically), so the list stays explicit and gets bumped when Vercel adds a version. For comparison, SvelteKit's Vercel adapter accepts any even major since sveltejs/kit#17570; the open-ended sveltejs/kit#17584 is not merged.
The v2 fix for Nuxt 4 is #4968.
📝 Checklist
🤖 Generated with Claude Code