Starting today, Node.js version 22 is available as the runtime for your builds and Vercel Functions leveraging Node. To use version 22, go to Project Settings > General > Node.js Version and select 22.x. This is also the default version for new projects.

Node.js 22 highlights:

• Improved Stream performance: higher default water mark provides performance boosts across the board at the cost of slightly higher memory usage

• Improved AbortSignal performance: optimized AbortSignal creation improves performance in fetch and the test runner

• Improved Buffer performance: significant improvements to the Buffer.copy and Buffer.write methods lead to overall performance boost

• Improved CJS interop with ESM: added support require()ing synchronous ESM graphs

The current version used by Vercel is 22.11.0 and will automatically update minor and patch releases. Therefore, only the major version (22.x) is guaranteed.

Read our Node.js runtime documentation to learn more.

Streaming is now supported and will soon be enabled by default in Vercel Functions for the Python runtime, allowing functions to send data to the client as it’s generated rather than waiting for the full response. This is particularly useful for AI applications.

This change will be rolled out progressively. Starting today, it will apply to all new projects and will take effect for all existing projects on January 5, 2025. On this date, projects using Log Drains will be migrated, and streaming responses will impact the format and frequency of runtime logs.

To enable streaming as the default for your Vercel Functions using Python, add the VERCEL_FORCE_PYTHON_STREAMING=1 environment variable in your project. Streaming will then be enabled on your next production deployment.

For more information, read the Python streaming documentation or get started with our template.

Pro customers can now set up to three regions for their Vercel Functions, enabling compute to run closer to distributed data sources for faster responses and improved performance. When multiple Vercel Function regions are configured, user requests that require compute will be routed to the closest specified region.

Previously, functions for Pro customers were restricted to a single region. Increasing to three regions enables:

• Global low-latency

• Maintaining high compute density leading to higher cache hit rates and lower cold starts

• Compatibility with standard database replication like Postgres read replicas

This also adds an extra layer of redundancy, complementing the built-in multi-Availability Zone redundancy of Vercel Functions.

To configure additional regions, add a regions property to your vercel.json.

{
  "regions": ["sfo1", "lhr1", "sin1"]
}

Redeploy your project for the changes to take effect. Learn more about configuring regions.