Skip to content

Work / Learning Platform / Wiki / Surfaces

error-boundary

Surfacecanonicalverified 2026-10-04

SURFACE.WEB.STATES.ERROR-BOUNDARY

Summary

What a route shows when rendering it throws.

Raw wireframe

  • .context/designs/web/states/500.html

Why it is drawn this way

One screen stands for four files. error.tsx under /courses, /courses/[courseSlug], /my-courses and /instructor/courses/[courseSlug] are the same 25 lines. Home, the auth pages and Settings have no boundary of their own.

"The team has been notified" is not true yet. The boundary calls console.error and nothing else. Error tracking is task 5.6 of FEAT-0005 and 8.1 of FEAT-0010, both open.

Go home is a full page load. It sets window.location.href, not the router, so the app restarts. Try again is a button here because it re-renders in place.

There is no 404. not-found.tsx renders nothing and pushes to /. routes.js records that under missing.

Related

Sources

  • apps/website/src/app/courses/error.tsx
  • apps/website/src/app/not-found.tsx