Error boundaries

What this means

An error boundary catches rendering errors below it and shows fallback UI instead of crashing the whole screen. Traditional error boundaries are class components, and frameworks often provide route-level error files.

In beginner terms, this topic answers one practical question: "What should I write, and why does React care about it?" Do not try to memorize the syntax first. First understand the idea, then connect the syntax to that idea.

Why it matters

Users need a clear recovery path when something fails. Error UI should explain the issue and offer a way to retry or navigate away.

When you build real React screens, this idea helps you decide where data should live, what the user should see, and what should happen after an interaction. That is why this lesson is part of the main path instead of being an optional detail.

Step by step

1. Notice the UI problem this topic solves. 2. Look at the smallest possible example. 3. Change one value and predict what should appear. 4. Run the example and compare the result with your prediction. 5. Use the practice task before moving on.

Small example

function ErrorFallback() {
  return <p>Something went wrong. Try again.</p>;
}

Common mistake

Do not expose technical stack traces to normal users. Keep detailed logs for developers and friendly messages for users.

Practice task

Write fallback copy for a lesson page that failed to load.

Remember this

Good error UI is honest and recoverable.