CatchBoundary for expected errors in Remix - Mini Project: Build & Apply

CatchBoundary for expected errors

📖 Scenario: You are building a simple Remix app that fetches user data from a server. Sometimes the server returns an error, like a 404 if the user is not found. You want to handle these expected errors gracefully by showing a friendly message instead of a crash.

🎯 Goal: Create a CatchBoundary component in Remix that catches expected errors and displays a user-friendly message. You will start by setting up a loader that throws an error for a missing user, then configure the CatchBoundary to handle that error.

📋 What You'll Learn

Create a loader function that throws a 404 response with a message 'User not found'.

Create a CatchBoundary component that uses useCatch() to get the caught response.

Display the caught status and statusText inside the CatchBoundary.

Ensure the CatchBoundary renders a friendly message when a 404 error is caught.

💡 Why This Matters

🌍 Real World

Handling expected errors gracefully in web apps improves user experience by showing clear messages instead of crashes.

💼 Career

Knowing how to use CatchBoundary in Remix is essential for building robust, user-friendly React web applications with server-side data loading.

1

Setup loader with error throwing

Create a loader function called loader that throws a 404 response with the message 'User not found' using throw new Response('User not found', { status: 404 }).

Remix

# Your code here

Hint

Use throw new Response('User not found', { status: 404 }) inside the loader function.

2

Create CatchBoundary component

Create a CatchBoundary component that calls useCatch() from @remix-run/react and stores the result in a variable called caught.

Remix

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

export async function loader() {
  throw new Response('User not found', { status: 404 });
}

// Your code here

Hint

Import useCatch and call it inside CatchBoundary to get the caught response.

3

Display caught status and statusText

Inside the CatchBoundary component, return a <div> that displays the caught status using {caught.status} and the status text using {caught.statusText}.

Remix

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

export async function loader() {
  throw new Response('User not found', { status: 404 });
}

export function CatchBoundary() {
  const caught = useCatch();
  // Your code here
}

Hint

Return JSX that shows caught.status and caught.statusText inside a <div>.

4

Add friendly message for 404 error

Update the CatchBoundary component to check if caught.status === 404. If true, display a friendly message: 'Sorry, the user you are looking for does not exist.' below the status and statusText.

Remix

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

export async function loader() {
  throw new Response('User not found', { status: 404 });
}

export function CatchBoundary() {
  const caught = useCatch();
  // Your code here
}

Hint

Use a conditional inside JSX to show the friendly message only when caught.status is 404.

Practice

1. What is the main purpose of a CatchBoundary in Remix Framework?

easy

A. To display user-friendly messages for expected errors without crashing the app

B. To catch all unexpected errors and log them to the server

C. To replace the default error page with a blank screen

D. To automatically retry failed network requests

Solution

1. Step 1: Understand the role of CatchBoundary

   CatchBoundary is designed to handle expected errors gracefully by showing friendly messages to users.

2. Step 2: Differentiate from other error handling

   Unlike unexpected errors that crash the app, CatchBoundary prevents crashes by catching known error responses.

3. Final Answer:

   To display user-friendly messages for expected errors without crashing the app -> Option A

4. Quick Check:

   CatchBoundary = user-friendly error display [OK]

Hint: CatchBoundary shows expected errors nicely, not crashes [OK]

Common Mistakes:

• Confusing CatchBoundary with global error logging
• Thinking it handles unexpected crashes
• Assuming it retries failed requests

2. Which of the following is the correct way to access error details inside a CatchBoundary component?

easy

A. const caught = useCatch();

B. const error = useError();

C. const error = useBoundary();

D. const caught = useErrorBoundary();

Solution

1. Step 1: Recall the hook for CatchBoundary

   Remix provides useCatch() to get error details inside CatchBoundary.

2. Step 2: Verify other options

   Hooks like useError(), useBoundary(), or useErrorBoundary() do not exist in Remix for this purpose.

3. Final Answer:

   const caught = useCatch(); -> Option A

4. Quick Check:

   useCatch() = error details in CatchBoundary [OK]

Hint: Remember: useCatch() gets error info in CatchBoundary [OK]

Common Mistakes:

• Using non-existent hooks like useError()
• Confusing useCatch() with useErrorBoundary()
• Trying to access error from props instead of hook

3. Given this CatchBoundary code snippet, what will be rendered if the caught status is 404?

export function CatchBoundary() {
  const caught = useCatch();
  return (
    <div>
      <h1>Error {caught.status}</h1>
      <p>{caught.statusText}</p>
    </div>
  );
}

medium

A. Error 404Page Missing

B. Error 500Internal Server Error

C. Error 404Not Found

D. ErrorUnknown Error

Solution

1. Step 1: Identify caught status and statusText

   The caught object has status 404 and statusText 'Not Found' by default for 404 errors.

2. Step 2: Match rendered output

   The component renders <h1>Error 404</h1> and <p>Not Found</p> exactly as in

   Error 404

   Not Found

   .

3. Final Answer:

   <h1>Error 404</h1><p>Not Found</p> -> Option C

4. Quick Check:

   caught.status = 404, caught.statusText = Not Found [OK]

Hint: Caught status and statusText show error info [OK]

Common Mistakes:

• Assuming statusText is 'Page Missing' instead of 'Not Found'
• Mixing up 404 with 500 error messages
• Ignoring caught.status and using static text

4. What is wrong with this CatchBoundary component code?

export function CatchBoundary() {
  const caught = useCatch;
  return (
    <div>Error: {caught.status}</div>
  );
}

medium

A. useCatch should be imported from react, not remix

B. Caught object does not have a status property

C. CatchBoundary must return a fragment, not a div

D. useCatch is not called as a function

Solution

1. Step 1: Check how useCatch is used

   The code assigns const caught = useCatch; without parentheses, so useCatch is not called.

2. Step 2: Understand consequences

   Without calling useCatch(), caught is a function reference, not the error object, causing runtime errors when accessing caught.status.

3. Final Answer:

   useCatch is not called as a function -> Option D

4. Quick Check:

   useCatch() must be called to get error info [OK]

Hint: Always call useCatch() with parentheses [OK]

Common Mistakes:

• Forgetting parentheses on useCatch()
• Assuming caught is error object without calling hook
• Incorrect import source for useCatch

5. You want to show a custom message for 401 Unauthorized errors inside a CatchBoundary. Which code snippet correctly implements this behavior? A)

export function CatchBoundary() {
  const caught = useCatch();
  if (caught.status === 401) {
    return <div>Please log in to access this page.</div>;
  }
  return <div>Error {caught.status}</div>;
}

B)

export function CatchBoundary() {
  const caught = useCatch();
  if (caught.status === 403) {
    return <div>Please log in to access this page.</div>;
  }
  return <div>Error {caught.status}</div>;
}

C)

export function CatchBoundary() {
  const caught = useCatch();
  if (caught.status === 401) {
    return <div>Access denied.</div>;
  }
  return <div>Error {caught.status}</div>;
}

D)

export function CatchBoundary() {
  const caught = useCatch();
  if (caught.status === 401) {
    return <div>Error 401 occurred.</div>;
  }
  return <div>Please log in to access this page.</div>;
}

hard

A. Shows 'Please log in to access this page.' only for 403 errors, else generic error

B. Shows 'Please log in to access this page.' only for 401 errors, else generic error

C. Shows 'Access denied.' for 401 errors, else generic error

D. Shows 'Error 401 occurred.' for 401 errors, else 'Please log in to access this page.'

Solution

1. Step 1: Identify the correct status code and message

   401 means Unauthorized, so the message should prompt login only for status 401.

2. Step 2: Check the conditional logic and fallback

   Shows 'Please log in to access this page.' only for 401 errors, else generic error correctly checks for 401 and shows the login message only then, otherwise shows a generic error with status.

3. Final Answer:

   Shows 'Please log in to access this page.' only for 401 errors, else generic error -> Option B

4. Quick Check:

   401 status triggers login prompt in CatchBoundary [OK]

Hint: Match status code 401 exactly for login message [OK]

Common Mistakes:

• Using wrong status code like 403
• Showing login message for all errors
• Mixing messages between conditions