/layout.js @ 1709036260701 [Home]

async Server Components

Server Components can be async, so they return a Promise. When rendering, RSC will wait for all Promises to resolve before returning the html content or Virtual DOM back to the browser. This is what caused the delay in the delivery of the content of this page. Reload to see how long it takes to return.

Below you can see a simple <Delay> Server Component:

export default async function Delay({seconds=1,children}) {
  return new Promise((resolve)=>{
        <div className={"box"}>
          Render Timestamp: {Date.now()}

This component creates a Promise that waits a certain number of seconds before resolving to a simple DIV with a timestamp showing when it rendered. If the component has children, they are then rendered.

And below is the output of multiple instances of this Component, some nested and some not:

Render Timestamp: 1709036261703
Render Timestamp: 1709036261703
Render Timestamp: 1709036261703
Render Timestamp: 1709036262205
Render Timestamp: 1709036262708
import Delay from "../Delay";
export default () => <>
  <Delay seconds={1}/>
  <Delay seconds={1}/>
  <Delay seconds={1}>
    <Delay seconds={.5}>
      <Delay seconds={.5}/>

Notice how the first 3 timestamps are either exactly or nearly identical. This demonstrates that async RSCs are rendered in parallel.

The nested components, however, have increasing timestamps. This is because the outer Delay resolved after 1 second. At that point, it rendered its children. Its child was another Delay component with a delay of 0.5 seconds. Once that time elapses, it renders and again calls its children to render. This is a third Delay component, with a delay of 0.5 seconds.

The nested components demonstrate that waterfalls can be created in Server Components, where the inner components do not begin their async operations until their parent is actually rendered.

If you reload this page you will see that it takes ~2 seconds to return its content.

The outer Delay is 1s, its child is 0.5s, and its child is again 0.5s. The waterfall causes the whole page to wait a total of 2 seconds to return content.

Forcing SSR instead of SSG

I want this page to run each time it is requested, so the delay is experienced by you. But recall that SSG is the default for RSC.

This means that by default, at build time RSC would realize that there is nothing on the page that must be run at request-time, like a database call or a fetch.

So, during the build it runs the component and waits for the delay to resolve, then takes the final html and virtual DOM and exports that. When the page is loaded by the user, they experience no delay. The delay happened at build time rather than request time.

We need a way to tell RSC to run this page each time it's requested, rather than just once at build time.

export const revalidate=0;

Putting this in the .js file is one way to tell NextJS that it needs to re-run (re-validate) the output of this page with every request. It is put on this page, but not most of the others in this tutorial.

Wait, is this PHP?!

No. Don't.

Years ago, this was the normal pattern for server-side content generation. The entire operation would need to complete before any content was returned back to the browser. Imagine a slow database call, or a remote API call, or a complex operation that requires loading many libraries to make calculations. The user would wait for the page to reload, just as you see here.

What if...

you could return the available content as soon as possible to immediately show to the user, and then as each Promise resolves fill in its content where it's supposed to go?

You can. This is called streaming, and it's one of the biggest benefits of React Server Components.

Streaming with Server-Side Suspense