• Server Actions in Next.js are now stable.

• Experimental Partial Prerendering will be introduced into Next.js 14.

• Next.js is 22% faster to start up your local server and 29% faster to see code updates after making changes.

• Turbopack is 53.3% faster to start up your local server and 94.7% faster to see code updates with Fast Refresh.

• A new course on Next.js Learn is available to teach the latest Next.js features.

Link to headingThe community that built Next.js

We have seen the Next.js community consistently growing over the years, and today, we're proud to say that over 850,000 developers choose to deploy with Next.js every day.

Our community continues to build some of the most ambitious sites on the web. Sites like Nike, Notion, Adobe, and even some of the most revolutionary AI projects like ChatGPT and Claude.

Thanks to the feedback and collaboration from the community as a whole, we've been able to release Next.js features incrementally like:

• The App Router, with more flexibility, support for nested routes and layouts.

• Powerful integrated system to fetch, cache, and revalidate data.

• A fast foundation, built on streaming HTTP responses.

As we’ve moved from the original Layouts RFC, to Beta, to stabilizing the APIs, we’ve seen continued adoption of the App Router across the top one million websites on the internet.

We want Next.js to be easy to use and easy to adopt. To help, we’ve updated Next.js Learn to teach the latest Next.js features mentioned above, as well as authentication, using a database, state management, and more to build a real application. This course will help the community to be able to explore and incrementally adopt new features we announced starting with Next.js 13.

Link to headingIntroducing Next.js 14

In introducing Next.js 14 to the world, we're excited to say it contains no new APIs.

We want to continue simplifying the framework and even make it possible to leave some APIs behind when you use Next.js App Router. With App Router's new fetching patterns, there is no need to learn Next.js specific functions, like getServerSideProps.

With Next.js 14, we also announced that Server Actions in Next.js are now stable. This is our recommended way of mutating data, that’s integrated into the fetching and caching layer in Next.js.

Companies like Clerk, Supabase, Shopify, Payload, Sanity, Okta, and more have embraced Server Components and soon Server Actions.

The performance improvements seen from adopting the App Router and Server Components have been promising. For example, the App Router helped luxury brand Jennifer Fisher move from a heavy ecommerce theme to a much faster headless storefront, built with Next.js.

Server Components helped them shift more work away from the device and back to the server, resulting in a faster initial paint and interactivity. This means their customers can more quickly add products to their cart, helping improve conversion rates and increase sales.

Link to headingContinued performance improvements

Since Next.js Conf 2022, we have made incredible strides in improving the compiler infrastructure. At the time, we announced that we were rewriting the Next.js CLI and bundler in Rust. We shipped a 22% faster initial compile (booting up the dev server and navigating to the first page) and a 29% faster code updates (saving code changes and seeing them on the screen).

In order to see the Next.js Compiler succeed with this new infrastructure, there are three things we will continue to monitor:

1. Fast dev server

2. Fast code updates

3. Fast builds

We’re running the entire test suite of Next.js that we've accumulated over seven years. We’ve seen that 90% of our 5,000 tests are passing with the Rust based Next.js Compiler. These tests allow us to continue to evolve and improve the Next.js Compiler while ensuring we’re not making regressions on expected functionality.

Let's talk about some of the performance improvements the Next.js Compiler is going to unlock. First, we're seeing 53% faster initial compile with the most recent introduction of Turbopack and up to 94% faster code updates. Again these apply to both routers (the Pages router and the App router).

This is the new baseline of performance and we will keep getting faster in the future. You can track our ongoing progress at AreWeTurboYet.com.

The goal of Next.js has always been to abstract away all of the complexity to get to a great developer experience in a way where you really didn't have to do anything else other than upgrade the framework to the latest version.

Link to headingAnnouncing Partial Prerendering

Partial Prerendering is a new rendering model that combines the benefits of fast Static Rendering and the personalization ability of Dynamic Rendering. It’s a natural progression of years of research into these previously at-odds rendering strategies—All without introducing any new APIs.

Here’s how it works:

When you build your application, Next.js will prerender a static shell for each page of your application, leaving holes for the dynamic content.

When a user visits a page, the fast static shell is served from a Vercel Region, allowing the user to start consuming the page, and the client and server to work in parallel. The client can start parsing scripts, stylesheets, fonts, and static markup while the server renders dynamic chunks using React’s new streaming architecture.

For Next.js applications, this means:

1. Fast Initial Visual - a cached static shell that loads swiftly for the user.

2. Fast Dynamic Visual - the client and server can work in parallel due to streaming, which facilitates quick rendering of dynamic content.

3. Great DX - It introduces no new APIs, making it easy to adopt without steep learning curves.

Partial Prerendering is the next step towards our ambitious goal of dynamic at the speed of static. Soon you’ll be able to leverage its benefits of a more personal, interactive, and dynamic web application without worrying about runtimes or regions.

Link to headingGet started today

Catch up on the rest of the videos from Next.js Conf 2023, browse our updated documentation and courses, and most importantly—tell us what you think. This community and this framework is stronger with your feedback and your ideas. Thanks for being part of this journey.