code-check-error-boundaries

Prevent blank screens by auditing route loaders for missing errorComponent definitions and ensuring React mutations have onError handlers or a global fallback to catch silent failures.

TanStack route loaders fail silently without an errorComponent because the router lacks a fallback UI to render, causing unhandled rejections that result in blank screens or infinite spinners.

Audit React mutation error handling by checking useMutation calls for onError definitions, verifying submit button pending-state safeguards, and flagging generic error toasts that lack retry affordances.

Silent corruption in fire-and-forget async callbacks occurs when unhandled promise rejections in background or webhook-style code paths bypass global fallbacks, leaving users without UI feedback or recovery paths.

A global error boundary is insufficient because route loaders, mutations, and fire-and-forget callbacks still require local errorComponent definitions and onError handlers to prevent non-recoverable UI states.

The best way to add UX recovery for async failures is to detect generic error toasts lacking retry options and implement targeted error boundaries with explicit recovery actions for routing and mutations.