What you need to know
An error boundary prevents one failed section from making the whole application feel broken. It can show a plain-language message and provide a reset action to try rendering again.
How to apply it
Add the route-level error file where a failure should be contained, keep its UI small and clear, and log diagnostic details safely on the server. Use not-found handling for missing content rather than generic errors.
Common mistake to avoid
Do not expose stack traces or secret configuration in an error page. Distinguish a missing route from an unexpected failure.