ErrorBoundary component in Remix - Mini Project: Build & Apply

Create an ErrorBoundary Component in Remix

📖 Scenario: You are building a Remix web app that needs to handle errors gracefully. Instead of showing a blank page or a confusing error message, you want to display a friendly message when something goes wrong in your app.

🎯 Goal: Build an ErrorBoundary component in Remix that catches errors and shows a simple error message to users.

📋 What You'll Learn

Create an ErrorBoundary component function

Use the error parameter to display the error message

Return a simple JSX structure with a heading and the error message

Export the ErrorBoundary component as default

💡 Why This Matters

🌍 Real World

Error boundaries help web apps show friendly messages instead of crashing or showing confusing errors.

💼 Career

Knowing how to handle errors gracefully is important for building reliable and user-friendly web applications.

1

Create the ErrorBoundary function

Create a function called ErrorBoundary that takes a single parameter named error.

Remix

// Your code here
// Create the ErrorBoundary function with error parameter

Hint

Remember, the function should receive an object with error as a property.

2

Add a simple error message JSX

Inside the ErrorBoundary function, return a div element containing an h1 with the text Something went wrong and a p element that displays the error.message.

Remix

export function ErrorBoundary({ error }) {
  // Return JSX with h1 and p showing error.message
  // Your code here
}

Hint

Use JSX syntax to return the elements inside parentheses.

3

Export the ErrorBoundary component

Add an export default statement to export the ErrorBoundary function as the default export.

Remix

export function ErrorBoundary({ error }) {
  return (
    
      Something went wrong
      {error.message}
    
  );
}

// Export ErrorBoundary as default
// Your code here

Hint

Use export default ErrorBoundary; at the end of the file.

4

Add basic styling and accessibility

Inside the returned div, add a role attribute with value alert to help screen readers notice the error message. Also, add inline style to center the text using style={{ textAlign: 'center', marginTop: '2rem' }}.

Remix

export function ErrorBoundary({ error }) {
  return (
    
      {/* Add role and style attributes here */}
      Something went wrong
      {error.message}
    
  );
}

export default ErrorBoundary;

Hint

Use role="alert" on the div and add the style object with textAlign and marginTop.

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