gacor: Node.js 26 LTS becomes available for Vercel builds and functions

Vercel says Node.js 26 is generally available for builds and Functions, with HTTP/2 fetch behavior and Temporal among the release changes.

Published October 29, 20263 min readHandmade on the workshop bench

A code editor displaying a Node.js project

Photo: Creator not recorded / Openverse (source not recorded)

Vercel announced Node.js 26 LTS as generally available for builds and Vercel Functions on October 29. The changelog notes HTTP/2 by default for built-in fetch when the remote server supports it, the Temporal API, and V8 14.6.

How existing projects select the runtime

New projects use Node.js 26 by default.
Existing projects whose engines.node range allows version 26 may move to it on a later deployment.
Teams that want to pin the runtime can set engines.node to 26.x and redeploy.

The announcement also documents an environment variable for Functions that need to retain HTTP/1.1 behavior. Test framework dependencies and outbound integrations before changing the runtime.

Check the current Node.js version documentation and project deployment settings for the exact version used by each build and function.

gacor: Node.js 26 LTS becomes available for Vercel builds and functions

How existing projects select the runtime

Keep reading