"use client"; /** * Route-level error boundary (QA issue #5/#6: "many unreeled errors" and * "navigating … became fail / leads to error page"). * * Before this existed, ANY uncaught error while a route segment was * rendering (a position-string math throw, an unguarded `.map` on a * `null` blocks list, …) crashed the segment with no recoverable UI — * Next.js's error overlay in dev, a blank shell in prod. This boundary * catches it at the route level, shows a recoverable card, and keeps the * rest of the app usable. `reset()` re-renders the segment; combined with * the fixes that removed the throwing call sites, a transient failure is * now a visible, retryable state instead of a dead page. * * MUST be a client component and must NOT import app-wide stores or * providers (it renders outside them by design). */ export default function RouteError({ error, reset }: { error: Error & { digest?: string }; reset: () => void; }) { return (

Something went wrong on this page

The page failed to load or render. Your content is safe — try again, or go back to the workspace.

{error?.digest ? (

Ref: {error.digest}

) : null}
Go home
); }