Skip to content

Commit fc45724

Browse files
committed
docs: add a note about Incremental Hydration to the @defer docs
1 parent f8d22a9 commit fc45724

File tree

1 file changed

+2
-2
lines changed
  • adev/src/content/guide/templates

1 file changed

+2
-2
lines changed

adev/src/content/guide/templates/defer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -323,9 +323,9 @@ it('should render a defer block in different states', async () => {
323323

324324
## How does `@defer` work with server-side rendering (SSR) and static-site generation (SSG)?
325325

326-
When rendering an application on the server (either using SSR or SSG), defer blocks always render their `@placeholder` (or nothing if a placeholder is not specified).
326+
By default, when rendering an application on the server (either using SSR or SSG), defer blocks always render their `@placeholder` (or nothing if a placeholder is not specified) and triggers are not invoked. On the client, the content of the `@placeholder` is hydrated and triggers are activated.
327327

328-
Triggers are ignored on the server.
328+
To render the main content of `@defer` blocks on the server (both SSR and SSG), you can enable [the Incremental Hydration feature](/guide/incremental-hydration) and configure `hydrate` triggers for the necessary blocks.
329329

330330
## Best practices for deferring views
331331

0 commit comments

Comments
 (0)