From f9dbd9693e49cfcc33d6a26e92f48e2db68e539e Mon Sep 17 00:00:00 2001 From: Tee Ming Date: Sun, 24 Sep 2023 00:30:21 +0800 Subject: [PATCH] docs: remove outdated part about prerendering when ssr is off (#10775) --- documentation/docs/20-core-concepts/40-page-options.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/documentation/docs/20-core-concepts/40-page-options.md b/documentation/docs/20-core-concepts/40-page-options.md index 8ed7eba2d3ea..90bb2cd6f28d 100644 --- a/documentation/docs/20-core-concepts/40-page-options.md +++ b/documentation/docs/20-core-concepts/40-page-options.md @@ -66,10 +66,6 @@ Accessing [`url.searchParams`](load#using-url-data-url) during prerendering is f Pages with [actions](form-actions) cannot be prerendered, because a server must be able to handle the action `POST` requests. -### Prerender and ssr - -If you set the [ssr option](#ssr) to `false`, each request will result in the same empty HTML shell. Since this would result in unnecessary work, SvelteKit defaults to prerendering any pages it finds where `prerender` is not explicitly set to `false`. - ### Route conflicts Because prerendering writes to the filesystem, it isn't possible to have two endpoints that would cause a directory and a file to have the same name. For example, `src/routes/foo/+server.js` and `src/routes/foo/bar/+server.js` would try to create `foo` and `foo/bar`, which is impossible.