From e5169f26c58cb9dbe49a8832e8e5639f915b686d Mon Sep 17 00:00:00 2001 From: Satvik Mishra <89024979+SatvikMishra08@users.noreply.github.com> Date: Tue, 6 Oct 2026 14:04:26 +0530 Subject: [PATCH] docs: note that a pending snippet skips SSR of boundary content (#18922) also remove an outdated note about needing a pending snippet for await --------- Co-authored-by: Satvik Mishra Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> --- documentation/docs/05-special-elements/01-svelte-boundary.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/05-special-elements/01-svelte-boundary.md b/documentation/docs/05-special-elements/01-svelte-boundary.md index 41ebee1564..8af7edfbd1 100644 --- a/documentation/docs/05-special-elements/01-svelte-boundary.md +++ b/documentation/docs/05-special-elements/01-svelte-boundary.md @@ -38,7 +38,7 @@ This snippet will be shown when the boundary is first created, and will remain v The `pending` snippet will _not_ be shown for subsequent async updates — for these, you can use [`$effect.pending()`]($effect#$effect.pending). -> [!NOTE] In the [playground](/playground), your app is rendered inside a boundary with an empty pending snippet, so that you can use `await` without having to create one. +> [!NOTE] During server-side rendering, a boundary with a `pending` snippet renders that snippet and ignores the rest of its content. See [Server-side rendering](await-expressions#Server-side-rendering). ### `failed`