Error Boundary
An error boundary catches a screen crash inside one part of a component tree. It shows a safe replacement there.
Another example
One chart crashes. Navigation and the other dashboard cards still work.
Main parts
- 01Protected subtree
- 02Caught error
- 03Local fallback
- 04Working siblings
- 05Reset action
Use it when
Place one around a screen area that can fail without stopping the whole page.
Do not use it when
Do not use it for normal form errors or failed requests. Handle those as expected states.
Name used in code
protected subtree + caught render error + fallback + reset Before you ship
Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback.
Outcome: Use or review Error Boundary as a technical building block that the team can maintain. User context: One chart crashes. Navigation and the other dashboard cards still work. Technology or engineering concept: Error Boundary. Why it fits: Place one around a screen area that can fail without stopping the whole page. Do not use it when: Do not use it for normal form errors or failed requests. Handle those as expected states. Engineering fit: Define where it runs and which version to use. Set its job, interfaces, data flow, dependencies, supported systems, security, and speed limits. Explain how it fits the current stack. Lifecycle safeguards: Check dependency health and licenses. Add monitoring and a fallback. Name the upgrade owner. Do not add a second tool for the same job without a measured benefit. Acceptance criteria: A small integration proves the needed behavior. Test compatibility, security, failure, and performance. Document deploy, upgrade, support, and rollback steps. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Current stack, runtime and version rules, target systems, dependency owner, performance budget, support period, and migration limits.
Check this request
Review the current use of Error Boundary. Definition: An error boundary catches a screen crash inside one part of a component tree. It shows a safe replacement there. Release checks: Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.