Node.js 20 is being deprecated on October 1, 2026
Mirrored from Vercel — AI for archival readability. Support the source by reading on the original site.
Following the Node.js 20 end of life on April 30, 2026, we are deprecating Node.js 20 for Builds and Functions on October 1, 2026.
How can I see which of my projects are affected?
You can see which of your projects are affected by this deprecation with:
npm i -g vercel@latestvercel project ls --update-requiredView projects that require updating.
Will my existing deployments be affected?
No, existing deployments with Serverless Functions will not be affected. Invocations to already-deployed functions will continue to work normally. Only new deployments will be affected.
When will I no longer be able to use Node.js 20?
On October 1, 2026, Node.js 20 will be disabled in Project Settings. Existing projects using 20 as the version for Functions will display an error when a new deployment is created.
How can I upgrade my Node.js version?
You can configure your Node.js version in Project Settings or through the engines field in package.json. Learn more about supported Node.js versions.
You can also hand the upgrade to your coding agent:
Upgrade this Vercel project from Node.js 20 to 24. Set the engines field in package.json to { "node": "24.x" }, which overrides the Project Settings version on the next deployment. Update any Node 20 pins in .nvmrc, .node-version, or CI configs. Switch the local runtime to Node 24, reinstall dependencies, run the build and tests, and fix any breaking changes. After deploying, confirm the version by logging process.version.Hand off to your coding agent to handle upgrading your project for you.
Upgrade before October 1, 2026. Learn more about supported Node.js versions.
Discussion (0)
Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.
Sign in →No comments yet. Sign in and be the first to say something.