Node.js 20 has reached end-of-life, and Vercel will disable it for Builds and Functions beginning October 1, 2026. For teams moving to Node.js 24, here's what to understand and validate before the next production deployment.
Node.js 20 reached end-of-life on April 30, 2026 and no longer receives normal upstream security and maintenance updates.
For organizations using Vercel, there is another important date approaching. Beginning October 1, 2026, Vercel will disable Node.js 20 for Builds and Functions. Projects still relying on that runtime will no longer be able to create new deployments normally.
Vercel recommends moving affected projects to Node.js 24, a current Long-Term Support release.
The migration may be straightforward for many applications. The important part is understanding where Node.js 20 is being used and validating the application before the change reaches production.
What Happens on October 1?
Existing Vercel deployments using Node.js 20 will not automatically stop running.
The change affects new Builds and Functions using the Node.js 20 runtime.
An application could therefore continue operating normally after the deadline, with the issue only becoming apparent when the team next needs to deploy a change.
That could be a routine release—or an urgent checkout fix, security update or integration change.
Identifying affected projects before October 1 helps prevent an outdated runtime from becoming a deployment constraint when a release is already needed.
What Works—and What Can Break?
Moving from Node.js 20 to Node.js 24 does not mean an application needs to be rebuilt.
Applications using current frameworks and actively maintained dependencies may require relatively little work. Standard JavaScript and TypeScript application functionality does not inherently need to be rewritten because the runtime changes.
The areas most likely to need attention are those that depend on a particular runtime version or older application behavior.
Dependencies and native modules Older packages may not support Node.js 24 or may require updating or rebuilding.
Deprecated or changed APIs Applications or dependencies relying on older Node.js behavior can expose compatibility issues after the upgrade.
Framework compatibility For applications using Next.js or another framework, teams should confirm that the installed framework version supports the target runtime.
Builds and serverless functions Build scripts and Vercel Functions may depend on Node.js even when much of the storefront itself runs in the browser.
CI/CD environments Updating Vercel does not automatically update the runtime used by development, testing or CI/CD systems.
Node.js 20 May Be Configured in More Than One Place
The runtime can be specified across several parts of an application's environment, including:
- Vercel Project Settings
package.json.nvmrcor.node-version- CI/CD configurations
- container configurations
- local development environments
Vercel specifically notes that a Node.js version defined through the engines field in package.json can override the version selected in Project Settings.
The goal should therefore be to align the runtime across development, testing, build and deployment environments, rather than changing one setting and assuming the migration is complete.
Commerce Applications Need More Than a Successful Build
For commerce applications, a successful Node.js 24 build is an important milestone—but it does not confirm that every business-critical workflow operates correctly.
Modern storefronts frequently connect with commerce platforms, ERP and PIM systems, payment and tax providers, search, authentication, fulfillment systems, middleware and custom APIs.
After upgrading, regression testing should focus on the workflows most important to customers and operations.
That includes:
- product search, navigation and product information
- pricing and inventory
- customer login and account functionality
- cart, checkout, tax, shipping and payments
- APIs and integrations
- serverless functions and webhooks
- custom workflows such as quoting, subscriptions or B2B purchasing
A runtime change does not mean these capabilities will break. They should simply be part of validation before production deployment.
A successful build tells you the application can build on Node.js 24. Business workflow testing tells you whether the commerce experience is ready to operate on it.
Node.js 20 to Node.js 24 Checklist
Before migrating an affected production application:
- [ ] Identify active Vercel projects still using Node.js 20.
- [ ] Check for Node.js 20 version pins across application and deployment configurations.
- [ ] Confirm framework and dependency compatibility with Node.js 24.
- [ ] Align local development, testing and CI/CD environments.
- [ ] Build and run automated tests using Node.js 24.
- [ ] Deploy to a preview or non-production environment.
- [ ] Test customer-critical workflows, APIs and integrations.
- [ ] Verify the runtime before deploying to production.
What If You Can't Migrate Before October 1?
Vercel provides an alternative for applications that cannot complete the migration before the deadline.
Applications deployed using container images can specify their own Node.js runtime rather than relying on Vercel's Node.js Project Setting. However, this transfers responsibility for managing the runtime and its security updates to the organization.
It can provide additional time in specific situations, but it does not change the underlying issue: Node.js 20 has reached end-of-life.
Use the Migration to Understand Application Health
Runtime upgrades are a normal part of maintaining modern applications.
If moving to Node.js 24 reveals outdated dependencies, unsupported frameworks, inconsistent environments or difficult-to-test integrations, those findings can help identify technical debt that may make future changes harder.
That doesn't mean a Node.js migration needs to become a modernization project.
Separate what you discover into:
What needs to change now. What needs to be tested now. What can be improved later.
For commerce teams, the immediate objective is clear: identify affected applications, move to a supported runtime and verify that the customer and operational workflows supported by the application continue working as expected.
Need Help Reviewing an Affected Commerce Application?
Arizon Digital works with businesses operating modern and headless commerce applications, including environments built with Next.js and deployed on Vercel.
If your team is preparing to move from Node.js 20 to Node.js 24, we can help assess the application, integrations and commerce workflows that should be reviewed before production deployment.
Talk to Arizon Digital about Node.js 24 readiness →
References
Vercel — Node.js 20 is being deprecated on October 1, 2026
https://vercel.com/changelog/node-js-20-is-being-deprecatedNode.js — Node.js Releases
https://nodejs.org/en/about/previous-releases