Private betaThis is the SIGSHIP beta. Everything here is live for testers; the public launch is in January.SIGSHIP private betaOpen the app →
  1. Home
  2. The 17 checks
  3. One crash takes down the whole screen
🧰 Launch hygiene · Nice to fix (SEV-3)

One crash takes down the whole screen 

In plain English: If one part of your page hits an error, the whole screen goes blank, and your user sees a white page with no explanation. An error boundary catches the error and shows a friendly message instead.

What happens if you ship it

A single bad record gives your users a white page, and nobody tells you.

How to fix it technical

Add a React error boundary around your routes, or error.tsx in a Next.js app, with a friendly message and a retry.

Let your AI tool fix it

Paste this into Lovable, Bolt, Cursor, Replit or Claude Code:

Prompt for your AI tool
Fix this problem in my project: One crash takes down the whole screen. Add a React error boundary around your routes, or error.tsx in a Next.js app, with a friendly message and a retry. Change only what this fix needs, then tell me what you changed and anything I have to do myself.

Check your app

Run npx sigship in your project folder. It reports this problem as no-error-boundary, along with 16 other checks. Nothing leaves your computer. New to the terminal?

Questions

What is an error boundary?

A React component that catches errors in the parts of the page inside it and shows a fallback, like "Something went wrong, try again", instead of a blank screen.

How do I add one in Next.js?

Add an error.tsx file next to your pages. Next.js uses it as the error boundary for that part of the app.

See every check · Jargon, explained