@sentry/ember

The Next.js SDK now supports error and performance monitoring for Next.js middleware and Edge API routes.
To set it up, add a sentry.edge.config.js or sentry.edge.config.ts file to the root of your project and initialize the SDK:

// sentry.edge.config.js or sentry.edge.config.ts

import * as Sentry from "@sentry/nextjs";

const SENTRY_DSN = process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN;

Sentry.init({
  dsn: SENTRY_DSN || "YOUR DSN HERE",
  tracesSampleRate: 1.0,
});

The Next.js will automatically instrument Edge API routes and middleware.
If you want to opt out of automatic instrumentation of middleware can use the autoInstrumentMiddleware option in the sentry object of your Next.js configuration:

const moduleExports = {
  sentry: {
    autoInstrumentMiddleware: false,
  },
};

Middleware can be manually instrumented by using the wrapMiddlewareWithSentry function.

• nextjs: Add Edge Runtime SDK

• nextjs: Add optional options argument to withSentryConfig as an alternative to the sentry property

• nextjs: Add edge route and middleware wrappers

• nextjs: Auto-wrap edge-routes and middleware

• replay: Update rrweb & rrweb-snapshot

• replay: Stop recording when retry fails

• replay: Stop without retry when receiving bad API response

• types: Add Trace Context type

• nextjs: Export isomorphic data fetching wrappers from client SDK

• nextjs: Make Next.js types isomorphic

• node: Handle node build without inspector in LocalVariables integration

• otel: Set trace context via Otel Span instead of Sentry span

• otel: Prevent baggage from being overwritten

• otel: Make sure we handle when sentry-trace is an empty array

• remix: Make remix SDK type exports isomorphic

• replay: Fix checkoutEveryNms

• replay: Fix incorrect uncompressed recording size due to encoding

• tracing: Attach request instrumentation span to active span instead of current transaction

• deprecated

  nextjs: Deprecate isBuild() and IS_BUILD