gem-hunter

react-error-boundary: Reusable React error boundary component. Supports all React renderers (including React DOM and React Native).

# npm
npm install react-error-boundary

# pnpm
pnpm add react-error-boundary

# yarn
yarn add react-error-boundary

Read the react-error-boundary docs for examples, API reference, and troubleshooting. The docs also include a frequently asked questions guide.

Wrap an ErrorBoundary around the part of the tree where you want to show a fallback UI if rendering fails. Your fallback can call resetErrorBoundary to clear the error and retry rendering:

"use client";

import { ErrorBoundary, getErrorMessage } from "react-error-boundary";

export default function App() {
  return (
    <ErrorBoundary
      fallbackRender={({ error, resetErrorBoundary }) => (
        <div role="alert">
          <p>Something went wrong:</p>
          <pre>{getErrorMessage(error)}</pre>
          <button onClick={resetErrorBoundary}>Try again</button>
        </div>
      )}
      onError={(error, info) => {
        // Log the error to your error reporting service
      }}
      onReset={() => {
        // Reset any state that may have caused the error
      }}
    >
      {/* Components protected by this boundary */}
    </ErrorBoundary>
  );
}

This package is built on top of React error boundaries, so it follows React's rules for what errors are caught.

Error boundaries catch errors thrown while rendering the tree below them.

Error boundaries do not catch errors from:

• Server-side rendering
• Event handlers
• The error boundary itself
• Async code that runs after rendering, like setTimeout callbacks or unresolved promises

For event handler errors and async callback errors:

• Use useErrorBoundary to pass caught errors to the nearest boundary.
• In React 19, useTransition Actions can be an alternative: errors thrown from a function passed to the returned startTransition function are caught by the nearest boundary.

"use client";

import { useTransition } from "react";
import { ErrorBoundary } from "react-error-boundary";

function AddCommentContainer() {
  return (
    <ErrorBoundary fallback={<p>Could not add comment</p>}>
      <AddCommentButton />
    </ErrorBoundary>
  );
}

function AddCommentButton() {
  const [isPending, startTransition] = useTransition();

  function handleClick() {
    startTransition(async () => {
      await addComment();
    });
  }

  return (
    <button disabled={isPending} onClick={handleClick}>
      {isPending ? "Adding..." : "Add comment"}
    </button>
  );
}

A reusable React error boundary component. Wrap this component around other React components to "catch" errors and render a fallback UI.

Catches errors thrown while rendering the tree below it.

Does not catch errors from:

• Server-side rendering
• Event handlers
• The error boundary itself
• Async code that runs after rendering, like setTimeout callbacks or unresolved promises

Event handler and async errors:

• Use useErrorBoundary to pass caught errors to the nearest boundary
• In React 19, errors thrown from a function passed to the startTransition function returned by useTransition are caught by the nearest boundary

ℹ️ The component provides several ways to render a fallback: fallback, fallbackRender, and FallbackComponent. Refer to the documentation to determine which is best for your application.

ℹ️ This is a client component. You can only pass props to it that are serializable or use it in files that have a "use client"; directive.

None

<ErrorBoundary fallback={<div className="text-red">Something went wrong</div>} />

<ErrorBoundary FallbackComponent={Fallback} />

<ErrorBoundary fallbackRender={({ error, resetErrorBoundary }) => <div>...</div>} />

This error can be caused by a version mismatch between react and @types/react. To fix this, ensure that both match exactly, e.g.:

If using NPM:

{
  ...
  "overrides": {
    "@types/react": "17.0.60"
  },
  ...
}

If using Yarn:

{
  ...
  "resolutions": {
    "@types/react": "17.0.60"
  },
  ...
}

This blog post shows more examples of how this package can be used, although it was written for the version 3 API.