From a6bd6e7619d04d789f6c1342b5cc41a10b0f037b Mon Sep 17 00:00:00 2001 From: Vedang Patel <120669538+VedangP57@users.noreply.github.com> Date: Thu, 19 Nov 2026 10:25:14 -0500 Subject: [PATCH] docs: use renderMode async in the prerender recipe --- src/routes/(5)guides/(9)choose-a-rendering-mode.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/routes/(5)guides/(9)choose-a-rendering-mode.mdx b/src/routes/(5)guides/(9)choose-a-rendering-mode.mdx index 2d7696ef5..b2824c05f 100644 --- a/src/routes/(5)guides/(9)choose-a-rendering-mode.mdx +++ b/src/routes/(5)guides/(9)choose-a-rendering-mode.mdx @@ -58,7 +58,7 @@ The host runs that handler on Node, a Fetch-based runtime, or a provider adapter import { serverFunctions } from "@solidjs/prerender/integration"; import { prerender } from "prerender-crawler/vite"; -solid({ start: true, ssr: true, serverFunctions: true }); +solid({ start: { renderMode: "async" }, ssr: true, serverFunctions: true }); prerender({ mode: "static", integrations: [serverFunctions()] }); ``` @@ -69,6 +69,10 @@ The server rendering happens once, during `vite build`. The `prerender-crawler` plugin starts at `/`, renders each page through the server build, writes the HTML, and follows same-origin links to find the rest. Server functions wrapped in `prerendered()` from `@solidjs/prerender` run during the build and their results are written as JSON files that the deployed client fetches instead of calling a server. +`renderMode: "async"` makes each page wait for every `Loading` boundary before it is written. +With the default `"stream"` mode, a page whose data is still loading when the shell is ready is written with the `Loading` fallback in place and the content in a `