bvaughn/react-error-boundary

Simple reusable React error boundary component

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 45 minutes ago
Added to GitGenius on September 8th, 2026
Created on July 18th, 2017
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 231
Total Stargazers: 7,988 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.2 hours
Mean response time: 25.4 hours
90th percentile: 3.0 days
Tracked items: 29

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 21% of issues opened in the past year have been closed. Three people close 90% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 1
Closed in 7 days: 1
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)
  • discussion (1)

Detailed Description

react-error-boundary is a reusable React error boundary component that wraps parts of your component tree to catch rendering errors and display fallback UI.

React error boundaries are a built-in mechanism for handling errors during rendering, but they require class components to implement. This library solves that by providing a simple component wrapper that works with functional components and supports all React renderers including React DOM and React Native. You wrap an ErrorBoundary around the section of your tree where you want error handling, and it catches errors thrown during rendering below it. When an error occurs, you can display a fallback UI and provide a reset function to retry rendering.

The tool is straightforward to adopt for any React project needing error handling during render. It works across different React environments and rendering targets. The library explicitly documents what it does and does not catch: it catches rendering errors but not errors from event handlers, server-side rendering, async callbacks like setTimeout, or errors within the boundary itself. The documentation includes examples, API reference, and a frequently asked questions guide.

The project maintains active engagement with users through sponsorship options and maintains clear, detailed documentation. Development appears focused on keeping the library lightweight and compatible across React versions and rendering targets, with specific attention to supporting both modern ES Module environments and older frameworks through version management.