Missing error state
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 component performs data fetching with no visible error handling, so failed requests likely fail silently in the UI.
Why it matters
If a fetch fails and the component ignores it, users just see missing content with no message and no way to retry. They cannot tell a failure from an empty result, and you hear about it as vague reports that the page is blank. Failed requests are routine on mobile networks, so this path gets exercised.
How to fix it
Catch failures and represent them in state: wrap fetch/axios calls in try/catch, check response.ok as well since fetch does not reject on HTTP error statuses, store the failure with useState, and render a short human message with a retry button. With TanStack Query or SWR, use the isError and error values the hook already returns.
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