docs: add clarification for SSR behavior of <svelte:boundary> pending snippet with remote functions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the problem
When a pending() snippet is present in a <svelte:boundary> it causes the data to not be server rendered, even if top-level awaited.
Resulting in Pending content shown client-side while promise resolves. This is not stated in the docs and causes confusion because to achieve the desired behavior you need to omit the pending snippet
See discord discussion: https://discord.com/channels/457912077277855764/1494203944208175104
Describe the proposed solution
- Mention SSR behavior on https://svelte.dev/docs/svelte/svelte-boundary#Properties-pending
- Mention same on Remote Functions page
Alternatives considered
Maybe a flow-chart to show how data is loaded in different scenerios?
Importance
nice to have
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the svelte:boundary Properties—pending documentation and the Remote Functions documentation on svelte.dev, using the reported SSR behavior as the starting point. Update both pages to explain when a pending snippet prevents server rendering and that omitting it enables the desired behavior; done means the clarification appears in both locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 75/100