ErrorBoundary component in Remix - Performance & Optimization

Performance: ErrorBoundary component

MEDIUM IMPACT

ErrorBoundary affects user experience by preventing full page crashes and controlling error rendering, impacting interaction responsiveness and visual stability.

Handling runtime errors in UI without crashing the entire app

Remix

import { useCatch } from '@remix-run/react';

export function ErrorBoundary() {
  const caught = useCatch();
  return (
    <div role="alert" aria-live="assertive">
      <h1>Error: {caught.status}</h1>
      <p>{caught.statusText}</p>
    </div>
  );
}

export default function App() {
  return <ErrorBoundary />;
}

Catches errors gracefully and renders fallback UI without full reload, improving responsiveness and visual stability.

📈 Performance GainAvoids full page reload; reduces INP and CLS; single render update instead of full reflow.

Handling runtime errors in UI without crashing the entire app

Remix

export function ErrorBoundary() {
  throw new Error('Crash!');
}

export default function App() {
  return <ErrorBoundary />;
}

No error catching; error crashes entire app causing full reload and poor user experience.

📉 Performance CostBlocks rendering completely; triggers full page reload; causes high INP and CLS.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No ErrorBoundary (app crash)	Full DOM reload	Multiple reflows	High paint cost	[X] Bad
ErrorBoundary with simple fallback UI	Minimal DOM update	Single reflow	Low paint cost	[OK] Good

Rendering Pipeline

ErrorBoundary intercepts errors during rendering or data loading, preventing the browser from crashing the entire app. It triggers a controlled re-render with fallback UI, affecting Layout and Paint stages.

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckLayout and Paint due to re-rendering fallback UI

Core Web Vital Affected

INP, CLS

ErrorBoundary affects user experience by preventing full page crashes and controlling error rendering, impacting interaction responsiveness and visual stability.

Optimization Tips

1Always use ErrorBoundary to catch errors and prevent full app crashes.

2Keep fallback UI minimal to reduce layout and paint costs.

3Test error states in DevTools Performance panel to ensure smooth recovery.

Performance Quiz - 3 Questions

What is the main performance benefit of using an ErrorBoundary component in Remix?

A It reduces the initial bundle size significantly.

B It prevents full page reloads on errors, improving interaction responsiveness.

C It speeds up CSS loading by deferring styles.

D It eliminates all JavaScript errors automatically.

DevTools: Performance

How to check: Record a session where an error occurs. Look for full page reloads or large layout shifts in the flame chart and summary.

What to look for: Check for reduced layout shifts and no full reloads when ErrorBoundary is used, indicating better INP and CLS.

Practice

1. What is the main purpose of an ErrorBoundary component in Remix?

easy

A. To fetch data from APIs before rendering components

B. To catch JavaScript errors in child components and display a fallback UI

C. To style components with CSS-in-JS

D. To manage user authentication state

Solution

1. Step 1: Understand ErrorBoundary role

   ErrorBoundary components catch errors thrown in their child components during rendering or lifecycle.

2. Step 2: Identify main purpose

   They prevent the entire app from crashing by showing a fallback UI instead of the broken component.

3. Final Answer:

   To catch JavaScript errors in child components and display a fallback UI -> Option B

4. Quick Check:

   ErrorBoundary catches errors = A [OK]

Hint: ErrorBoundary handles errors, not data or styles [OK]

Common Mistakes:

• Confusing ErrorBoundary with data fetching
• Thinking it manages styles or authentication
• Assuming it fixes errors automatically

2. Which of the following is the correct way to define an ErrorBoundary component in Remix?

easy

A. export function ErrorBoundary({ error }) { return {error.message}; }

B. export function ErrorBoundary() { return No error; }

C. export function ErrorBoundary({ data }) { return {data}; }

D. export function ErrorBoundary({ props }) { return {props.error}; }

Solution

1. Step 1: Check parameter usage

   ErrorBoundary receives an error prop with error details, so the parameter must be { error }.

2. Step 2: Verify returned JSX

   The component should display error.message to show the error text.

3. Final Answer:

   export function ErrorBoundary({ error }) { return <div>{error.message}</div>; } -> Option A

4. Quick Check:

   Use { error } prop and show error.message [OK]

Hint: ErrorBoundary gets error prop, not data or props object [OK]

Common Mistakes:

• Using wrong parameter name like data or props
• Not accessing error.message correctly
• Returning static text instead of error info

3. Given this ErrorBoundary component, what will be rendered if an error with message "Failed to load" occurs?

export function ErrorBoundary({ error }) {
  return (
    <div role="alert">
      <h2>Oops!</h2>
      <p>{error.message}</p>
    </div>
  );
}

medium

A. Oops!No error

B. ErrorUnknown error

C. Oops!Failed to load

D. Nothing renders because error is not handled

Solution

1. Step 1: Identify error message usage

   The component renders {error.message} inside a paragraph, so the actual error message will appear.

2. Step 2: Check rendered structure

   The output includes a div with role alert, an h2 with "Oops!", and a paragraph with the error message.

3. Final Answer:

   <div role="alert"><h2>Oops!</h2><p>Failed to load</p></div> -> Option C

4. Quick Check:

   Error message shown inside alert div = A [OK]

Hint: ErrorBoundary shows error.message inside fallback UI [OK]

Common Mistakes:

• Ignoring error.message and showing static text
• Missing role="alert" for accessibility
• Assuming no output if error occurs

4. What is wrong with this ErrorBoundary component code?

export function ErrorBoundary(error) {
  return <div>Error: {error.message}</div>;
}

medium

A. The error parameter should be destructured as { error }, but here it is a plain parameter

B. The error parameter should be destructured as { error }

C. The error parameter should be destructured as { error } but it is not

D. The component must return null on error

Solution

1. Step 1: Check parameter syntax

   ErrorBoundary receives props as an object, so the parameter should be destructured like { error }, not a plain variable.

2. Step 2: Identify correct destructuring

   Using error directly means it is the whole props object, so error.message will be undefined or cause error.

3. Final Answer:

   The error parameter should be destructured as { error }, but here it is a plain parameter -> Option A

4. Quick Check:

   Destructure props as { error } in ErrorBoundary [OK]

Hint: Destructure error prop: use ({ error }) not (error) [OK]

Common Mistakes:

• Using plain parameter instead of destructuring
• Returning null instead of fallback UI
• Confusing error prop with other props

5. You want to create an ErrorBoundary that shows a custom message for network errors and a generic message for others. Which code correctly implements this behavior?

export function ErrorBoundary({ error }) {
  if (error.message.includes('Network')) {
    return <div>Network error occurred. Please try again.</div>;
  }
  return <div>Something went wrong.</div>;
}

hard

A. The error prop should be named props, not error

B. This code will crash if error.message is undefined

C. The if condition should check error.type, not error.message

D. This code correctly shows a custom message for network errors and generic for others

Solution

1. Step 1: Analyze error message check

   The code checks if error.message contains 'Network' to show a specific message.

2. Step 2: Verify fallback message

   If the error is not a network error, it shows a generic fallback message, which is correct behavior.

3. Final Answer:

   This code correctly shows a custom message for network errors and generic for others -> Option D

4. Quick Check:

   Conditional error messages based on error.message = C [OK]

Hint: Check error.message content to customize fallback UI [OK]

Common Mistakes:

• Assuming error.message can be undefined without check
• Using wrong prop name instead of error
• Checking wrong error property like error.type