Set up Sentry observability for Next.js runtime paths

[Copilot]

This PR adds first-pass Sentry integration to the Next.js app so client navigation, server runtime, and edge runtime errors/performance signals are captured through a single configuration path. It also introduces explicit env knobs for DSN and trace sampling.

• SDK + framework wiring

  • Added @sentry/nextjs dependency.
  • Wrapped Next config with withSentryConfig(...) in next.config.js to enable Sentry build/runtime integration.

• Runtime initialization across execution targets

  • Added instrumentation.ts to register runtime-specific Sentry configs.
  • Added sentry.server.config.ts and sentry.edge.config.ts for server/edge initialization.
  • Added instrumentation-client.ts for browser initialization and router transition capture.

• Sampling + environment configuration

  • Added SENTRY_DSN and NEXT_PUBLIC_SENTRY_DSN.
  • Added SENTRY_TRACES_SAMPLE_RATE and NEXT_PUBLIC_SENTRY_TRACES_SAMPLE_RATE (default 0.1 in example env).
  • Runtime sampling values are parsed from env with fallback behavior.

// instrumentation.ts
export async function register() {
  if (process.env.NEXT_RUNTIME === "nodejs") await import("./sentry.server.config");
  if (process.env.NEXT_RUNTIME === "edge") await import("./sentry.edge.config");
}

export const onRequestError = Sentry.captureRequestError;

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
solar-car-website-next	Ready	Preview, Comment	May 23, 2026 4:40pm