sentry-nextjs-sdk

Run npx @sentry/wizard@latest -i nextjs for automated setup, or manually install @sentry/nextjs and create instrumentation-client.ts, sentry.server.config.ts, sentry.edge.config.ts, and instrumentation.ts. Then wrap next.config with withSentryConfig.

Next.js catches errors in error.tsx and global-error.tsx before Sentry sees them, so you must call Sentry.captureException(error) inside a useEffect in those files. Unhandled errors outside boundaries are captured automatically.

Yes, both routers are supported on Next.js 13+. App Router uses global-error.tsx for root errors, while Pages Router uses pages/_error.tsx with captureUnderscoreErrorException. Note that automaticVercelMonitors only works with Pages Router.

Source maps are not being uploaded during the build. Set SENTRY_AUTH_TOKEN as a build-time secret and configure authToken plus widenClientFileUpload in withSentryConfig, then run next build and check for source map upload output.

You need to export onRequestError from instrumentation.ts using Sentry.captureRequestError. This requires @sentry/nextjs version 8.28.0 or higher and Next.js 15 or later.

Tracing works, but the webpack.treeshake options in withSentryConfig only apply to webpack builds. Remove tree-shaking options when using Turbopack, which requires Next.js 15 or later for Sentry support.