'use client'; import { useEffect } from 'react'; /** * The last resort: rendered when the root layout itself throws, which * `app/error.tsx` cannot catch — it is rendered *inside* that layout. The * layout reads the config and the request headers, so this is not a theoretical * case; without this file such a failure renders a blank page. * * Everything here is deliberately self-contained: it replaces the whole * document, so `globals.css` and the theme custom properties are not * guaranteed to be in scope. No config lookup, no `next/link` (there is no * router shell to speak of), no shared components. Same wording as * `app/error.tsx`, which explains why it does not name a cause: production * builds replace the message with a digest, so the component genuinely cannot * tell an Immich outage from anything else. */ export default function GlobalError({ error, reset, }: { error: Error & { digest?: string }; reset: () => void; }) { useEffect(() => { console.error('[Folio] Root layout render failed:', error); }, [error]); return (

Something went wrong

This site could not be loaded right now. It is usually temporary — try again in a moment.

{/* A plain , not next/link: a full document request is exactly what is wanted here — a client-side transition would stay inside the tree whose root layout just failed. */} {/* eslint-disable-next-line @next/next/no-html-link-for-pages */} Back to the gallery
{error.digest && (

Reference: {error.digest}

)}
); }