Next.js 14 Released: Stable Server Actions and Partial Prerendering Preview
Next.js 14 made Server Actions stable, previewed Partial Prerendering, and delivered large Turbopack speedups for local development.
Historical Archive. This article documents an event from 2023 and is preserved with its original date for reference. It is not current news, and details may have changed since publication.
What happened
Next.js 14 was released on October 26, 2023, announced at Next.js Conf and on the official blog. Vercel described it as its most focused release, concentrating on performance and stabilising features rather than adding a large surface of new APIs.
Stable Server Actions
The headline is that Server Actions became stable. Server Actions let developers define functions that run securely on the server and are called directly from React components, replacing the need to hand-write an API route for many data mutations. Built on web fundamentals like forms and the FormData API, they integrate with the App Router's caching and revalidation, so mutating data, re-rendering, or redirecting can happen in a single network round-trip.
Partial Prerendering preview
Next.js 14 previewed Partial Prerendering, a compiler optimisation that serves a fast static shell immediately and streams in dynamic, personalised content within the same HTTP request. It is defined by React Suspense boundaries and requires no new APIs to learn, building on years of work in SSR, SSG and incremental static regeneration. It shipped as a preview, with more to come in later minor releases.
Turbopack and other changes
The release reported that 5,000 integration tests for next dev were passing with Turbopack, the Rust-based successor to webpack, with Vercel measuring large improvements in local server startup and Fast Refresh on its own site. Next.js 14 also decoupled blocking and non-blocking metadata, introduced new viewport and generateViewport exports, and raised the minimum Node.js version to 18.17. A free Next.js Learn course accompanied the release.
Why it mattered
Next.js 14 solidified the App Router story: stable Server Actions gave teams a production-ready way to handle mutations without separate API routes, while the Partial Prerendering preview signalled the framework's direction for combining static speed with dynamic personalisation. The Turbopack progress promised faster local iteration as it approached full stability.
Related on Skillo
See also: Next.js 13 and the App Router, Next.js 15's async request APIs.
Sources
Published date reflects the original event date (2023-10-26). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.
Written by
Skillo Staff
0 Comments
Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.