Root error boundary wraps entire application

Without a root error boundary, any unhandled React component error produces a white screen of death — the entire application unmounts silently. Users lose their context, their unsaved work, and often assume the product is broken. ISO 25010 reliability.fault-tolerance requires the system to continue operating under fault conditions; a missing root boundary violates that baseline. One null-pointer in a third-party widget can take down checkout, dashboard, and every other route.

Add app/error.tsx (Next.js App Router) or wrap your root component with react-error-boundary. The boundary must render a fallback — not just log — to satisfy the pass criteria.

// app/error.tsx — root error boundary
'use client'
export default function Error({
  error,
  reset,
}: {
  error: Error & { digest?: string }
  reset: () => void
}) {
  return (
    <div>
      <h1>Something went wrong</h1>
      <button onClick={reset}>Try again</button>
    </div>
  )
}

For non-Next.js apps, wrap your root render in src/main.tsx with <ErrorBoundary FallbackComponent={RootFallback}>.