Skip to content
← Back to Changelog

Thursday, October 26th 2023

Next.js 14 on Vercel

Posted by

Avatar for timvercel

Tim Neutkens

Software Engineer

Avatar for delbaoliveira

Delba de Oliveira

Staff Developer Advocate

Avatar for sokra

Tobias Koppers

Software Engineer

Avatar for jj4

JJ Kasper

Software Engineer

Avatar for feedthejim

Jimmy Lai

Software Engineer

Avatar for lubakravche

Luba Kravchenko

Software Engineer

Avatar for falcoagustin

Agustin Falco

Avatar for nabeel-sulieman

Nabeel Sulieman

Software Engineer

Next.js 14 is fully supported on Vercel. Build data-driven, personalized experiences for your visitors with Next.js, and automatically deploy to Vercel with optimizations, including:

  • Streaming: The Next.js App Router natively supports streaming responses. Display instant loading states and stream in units of UI as they are rendered. Streaming is possible for Node.js and Edge runtimes—with no code changes—with Vercel Functions.
  • React Server Components: Server Components allow you to define data fetching at the component level, and easily express your caching and revalidation strategies. On Vercel, this is supported natively with Vercel Functions and the Vercel Data Cache, a new caching architecture that can store both static content and data fetches.
  • React Server Actions: Server Actions enable you to skip manually writing APIs and instead call JavaScript functions directly for data mutations. On Vercel, Server Actions use Vercel Functions.
  • Partial Prerendering (Experimental): A new compiler optimization for dynamic content with a fast initial static response based on a decade of research and development into server-side rendering (SSR), static-site generation (SSG), and incremental static revalidation (ISR).

Additionally in Next.js 14 you will find:

  • Turbopack: 5,000 tests passing for App & Pages Router with 53.3% faster local server startup and 94.7% faster code updates with Fast Refresh.
  • Forms and mutations: The user experience is improved when the user has a slow network connection, or when submitting a form from a lower powered device.
  • Metadata: Blocking and non-blocking metadata are now decoupled. Only a small subset of metadata options are blocking, and we ensured non-blocking metadata will not prevent a partially prerendered page from serving the static shell.
  • Logging: More verbose logging around fetch caching can be enabled.
  • create-next-app: There is now an 80% smaller function size for a basic create-next-app application.
  • Memory management: Enhanced memory management is available when using edge runtime in development.

Check out our documentation to learn more.