Will It Vibe?No error boundary in a React app
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A React project with no error boundary anywhere means a single thrown error during render tears down the entire component tree and shows the user a blank page. Heuristic: it looks for componentDidCatch, getDerivedStateFromError, or the react-error-boundary library.
Why it matters
With no error boundary anywhere in the app, a single error thrown while rendering any component unmounts the entire React tree and leaves the user staring at a blank white page with no way to recover. Error boundaries let you catch render errors and show a fallback for just the broken part. This is a heuristic that looks for componentDidCatch, getDerivedStateFromError, or the react-error-boundary library.
How to fix it
Add at least one error boundary near the top of the app and, ideally, around independent sections (routes, widgets) so one failure does not take down everything. Use a class component with getDerivedStateFromError and componentDidCatch, or adopt the react-error-boundary library, and render a helpful fallback UI.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo