Skip to main content
tc

Error pages

Family-aware ErrorPage, NotFound404, live playground.

# Standalone error pages

Full-page error views are served by their own routes — the way consumers render them: one handler call per HTTP status, a real status code, the page inside the app's own layout shell.

404 — Page not found /errors/404404 — Dedicated NotFound404 /errors/404-page403 — Access denied /errors/403400 — Bad request /errors/400409 — Conflict /errors/409500 — Internal error /errors/500503 — Service unavailable /errors/503Full model — context, causes, trace /errors/full

# ErrorPage playground (live render)

Pick a family and fields, submit, and the route renders a real ErrorPage at the real HTTP status — a stateless GET form, nothing stored.

# ErrorAlert (by family)

# ErrorDetail (with context + cause chain)