Next.js › Error Handling & Not Found Pages

How would you set up a comprehensive error handling strategy across a large Next.js application with many route segments?

Advanced

Answer

You place error.js files at strategic points in your route structure, such as near features that are more likely to fail, use a shared error reporting service to log errors to a monitoring tool, provide clear and actionable messages for users, and include a global-error.js as a final safety net for anything that escapes the nested boundaries.
'use client';
import { useEffect } from 'react';
import { logErrorToService } from '@/lib/monitoring';

export default function Error({ error, reset }) {
  useEffect(() => {
    logErrorToService(error);
  }, [error]);
  return <button onClick={() => reset()}>Try again</button>;
}
Real-world example A large e-commerce platform places error boundaries around its checkout flow specifically, since that feature is business critical, while also logging every error to a monitoring service so the team is alerted quickly.

Common follow-ups: What monitoring tools are commonly used to track errors in production Next.js apps?;How do you avoid showing overly technical error details to end users?