error-tracking-nextjs

To add PostHog error tracking to Next.js, configure PostHog with environment variables for your project token and host, enable exception autocapture in the instrumentation file, and add manual captures at error boundaries and catch blocks for comprehensive client-side and server-side monitoring.

Uploading source maps for Next.js exception tracking ensures that captured stack traces resolve to your original source code rather than minified production bundles, making it significantly easier to identify, group, and debug issues quickly within PostHog.

Yes, PostHog error tracking supports both the Next.js App Router and Pages Router. You can instrument request errors and error boundaries across both routing architectures to capture and group server-side and client-side exceptions effectively.

Yes, PostHog error tracking supports automatic exception capture in Next.js. You must enable exception autocapture during the initial PostHog configuration before adding manual capture calls to ensure all unexpected errors are grouped into actionable issues.

The best way to configure PostHog error tracking in Next.js 15.3+ is by using the instrumentation-client.ts approach. This allows you to initialize PostHog with environment variables, enable exception autocapture, and set up source map uploads for accurate stack traces.

Minified stack traces in PostHog appear when source maps are not uploaded. You must upload source maps during your Next.js build process so PostHog can resolve the minified production errors back to your original source code for faster debugging.