You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/docs/11-page-options.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ If both are specified, per-page settings override per-app settings in case of co
12
12
13
13
SvelteKit includes a [client-side router](#appendix-routing) that intercepts navigations (from the user clicking on links, or interacting with the back/forward buttons) and updates the page contents, rather than letting the browser handle the navigation by reloading.
14
14
15
-
In certain circumstances you might need to disable [client-side routing](#appendix-routing) with the app-wide [`router` config option](#configuration-router) or the page-level `router` export:
15
+
In certain circumstances you might need to disable [client-side routing](#appendix-routing) with the app-wide [`browser.router` config option](#configuration-browser) or the page-level `router` export:
16
16
17
17
```html
18
18
<scriptcontext="module">
@@ -24,7 +24,7 @@ Note that this will disable client-side routing for any navigation from this pag
24
24
25
25
### hydrate
26
26
27
-
Ordinarily, SvelteKit [hydrates](#appendix-hydration) your server-rendered HTML into an interactive page. Some pages don't require JavaScript at all — many blog posts and 'about' pages fall into this category. In these cases you can skip hydration when the app boots up with the app-wide [`hydrate` config option](#configuration-hydrate) or the page-level `hydrate` export:
27
+
Ordinarily, SvelteKit [hydrates](#appendix-hydration) your server-rendered HTML into an interactive page. Some pages don't require JavaScript at all — many blog posts and 'about' pages fall into this category. In these cases you can skip hydration when the app boots up with the app-wide [`browser.hydrate` config option](#configuration-browser) or the page-level `hydrate` export:
The directory relative to `paths.assets` where the built JS and CSS (and imported assets) are served from. (The filenames therein contain content-based hashes, meaning they can be cached indefinitely). Must not start or end with `/`.
93
95
96
+
### browser
97
+
98
+
An object containing zero or more of the following `boolean` values:
99
+
100
+
-`hydrate` — whether to [hydrate](#page-options-hydrate) the server-rendered HTML with a client-side app. (It's rare that you would set this to `false` on an app-wide basis.)
101
+
-`router` — enables or disables the client-side [router](#page-options-router) app-wide.
102
+
94
103
### csp
95
104
96
105
An object containing zero or more of the following values:
> This only applies to server-rendered responses — headers for prerendered pages (e.g. created with [adapter-static](https://github.com/sveltejs/kit/tree/master/packages/adapter-static)) are determined by the hosting platform.
139
148
140
-
### hydrate
141
-
142
-
Whether to [hydrate](#page-options-hydrate) the server-rendered HTML with a client-side app. (It's rare that you would set this to `false` on an app-wide basis.)
143
-
144
149
### inlineStyleThreshold
145
150
146
151
Inline CSS inside a `<style>` block at the head of the HTML. This option is a number that specifies the maximum length of a CSS file to be inlined. All CSS files needed for the page and smaller than this value are merged and inlined in a `<style>` block.
@@ -223,10 +228,6 @@ See [Prerendering](#page-options-prerender). An object containing zero or more o
A`(filepath: string) => boolean`function that determines which files create routes and which are treated as [private modules](#routing-private-modules).
0 commit comments