docs: ErrorBoundary makes erroring routes uncacheable — document after RC
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22.1k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 52
Description
An SSR-caught <ErrorBoundary> error still responds 200, so the router sends Cache-Control: no-store and skips its SSR cache (#8745). A route is not cached while it errors, which can increase SSR costs if the error happens to all active users all at once.
Document after RC: the cost, and the way out — throw the failure as an error response (httpError()) instead of an inline fallback.
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
Start by locating the documentation entry points for ErrorBoundary and httpError, then review the SSR behavior described in #8745. Document the no-store and SSR cost consequence, and explain that throwing httpError() is the alternative to an inline fallback; mark it done when both the cost and workaround are covered after RC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100