Skip to content

Commit cc91ed1

Browse files
authored
Apply suggestion from @teemingc
1 parent f861131 commit cc91ed1

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

documentation/docs/20-core-concepts/40-page-options.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,6 @@ export const ssr = false;
129129

130130
If you add `export const ssr = false` to your root `+layout.js`, your entire app will only be rendered on the client — which essentially means you turn your app into an [SPA](glossary#SPA). You should not do this if your goal is to build a (statically generated site)[glossary#SSG].
131131

132-
133132
> [!NOTE] If all your page options are boolean or string literal values, SvelteKit will evaluate them statically. If not, it will import your `+page.js` or `+layout.js` file on the server (both at build time, and at runtime if your app isn't fully static) so it can evaluate the options. In the second case, browser-only code must not run when the module is loaded. In practice, this means you should import browser-only code in your `+page.svelte` or `+layout.svelte` file instead.
134133
135134
## csr

0 commit comments

Comments
 (0)