'use client'
/**
* Root error boundary (replaces the ROOT LAYOUT when it or something above the
* per-segment error.tsx throws, e.g. a render error during hydration/layout).
*
* Without this file, such an error falls through to Next.js's built-in fallback,
* which shows the bare "Application error: a client-side exception has occurred"
* white screen. That is exactly what surfaced when a starved orchestrator fed the
* page unexpected/hung data. global-error.tsx must render its own /
* because it stands in for the root layout, and it only runs in production.
*
* It carries no dependency on the app's global stylesheet (that lives in the
* layout it is replacing), so all styling is inline and self-contained.
*/
import { useEffect } from 'react'
const isChunkLoadError = (error: Error) =>
error.name === 'ChunkLoadError' ||
/Loading chunk [\w/.-]+ failed/i.test(error.message) ||
/Failed to load chunk/i.test(error.message)
export default function GlobalError({
error,
reset,
}: {
error: Error & { digest?: string }
reset: () => void
}) {
useEffect(() => {
// A stale/rotated build chunk after a redeploy: a hard reload recovers it.
if (isChunkLoadError(error)) {
window.location.reload()
return
}
console.error('Global error boundary:', error)
}, [error])
return (
Something went wrong
The application hit an unexpected error. The backend may be busy
(for example while large scans are running). Please try again in a
few seconds.