fix: add React error boundary to prevent full-page crashes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 12h 29m
- Merged PRs (30d)
- 12
Description
Problem
App.tsx has no React error boundary. If any component in the render tree throws (bad MDX, missing data, theme component error), the entire page goes blank with a console error. There's also no hydration error recovery in entry-client.tsx — hydration failure results in a blank page.
Suggested Fix
- Add an error boundary component wrapping the main content area in
App.tsx - Show a user-friendly error state with the page title and a "reload" option
- In
entry-client.tsx, catch hydration errors and fall back to client-side rendering instead of showing nothing
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading App.tsx to identify the main content area and entry-client.tsx to understand the current hydration flow. Reproduce or inspect the blank-page behavior, then verify that render errors show a user-friendly state with the page title and reload option, while hydration failures fall back to client-side rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100