@sentry/vercel-edge

Official Sentry SDK for Vercel Edge Runtime [ALPHA]

Links

• Official SDK Docs
• TypeDoc

Note: This SDK is still in an alpha state. Breaking changes can occur at any time.

Usage

To use this SDK, call init(options) as early as possible in the main entry module. This will initialize the SDK and hook into the environment. Note that you can turn off almost all side effects using the respective options.

// CJS Syntax
const Sentry = require('@sentry/vercel-edge');
// ESM Syntax
import * as Sentry from '@sentry/vercel-edge';

Sentry.init({
  dsn: '__DSN__',
  // ...
});

To set context information or send manual events, use the exported functions of @sentry/vercel-edge. Note that these functions will not perform any action before you have called init():

// Set user information, as well as tags and further extras
Sentry.setExtra('battery', 0.7);
Sentry.setTag('user_mode', 'admin');
Sentry.setUser({ id: '4711' });

// Add a breadcrumb for future events
Sentry.addBreadcrumb({
  message: 'My Breadcrumb',
  // ...
});

// Capture exceptions, messages or manual events
Sentry.captureMessage('Hello, world!');
Sentry.captureException(new Error('Good bye'));
Sentry.captureEvent({
  message: 'Manual',
  stacktrace: [
    // ...
  ],
});

Changelog

8.0.0-alpha.7

This is the seventh alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.

Read the in-depth migration guide to find out how to address any breaking changes in your code.

Important Changes

• feat(nextjs): Use OpenTelemetry for performance monitoring and tracing (#11016)

We now use OpenTelemetry under the hood to power performance monitoring and tracing in the Next.js SDK.

• feat(v8/gatsby): Update SDK initialization for gatsby (#11292)

In v8, you cannot initialize the SDK anymore via Gatsby plugin options. Instead, you have to configure the SDK in a sentry.config.js file.

We also removed the automatic initialization of browserTracingIntegration. You now have to add this integration yourself.

Removal/Refactoring of deprecated functionality

• feat(v8): Remove addGlobalEventProcessor (#11255)
• feat(v8): Remove deprecated span id fields (#11180)
• feat(v8): Remove makeMain export (#11278)
• feat(v8/core): Remove deprecated span.sampled (#11274)
• feat(v8/core): Remove getActiveTransaction (#11280)
• feat(v8/core): Remove spanMetadata field (#11271)
• feat(v8/ember): Remove deprecated StartTransactionFunction (#11270)
• feat(v8/replay): Remove deprecated replay options (#11268)
• feat(v8/svelte): Remove deprecated componentTrackingPreprocessor export (#11277)
• ref: Remove more usages of getCurrentHub in the codebase (#11281)
• ref(core): Remove scope.setSpan() and scope.getSpan() methods (#11051)
• ref(profiling-node): Remove usage of getCurrentHub (#11275)
• ref(v8): change integration.setupOnce signature (#11238)
• ref: remove node-experimental references (#11290)

Other Changes

• feat(feedback): Make "required" text for input elements configurable (#11152) (#11153)
• feat(feedback): Update user feedback screenshot and cropping to align with designs (#11227)
• feat(nextjs): Remove runtime and vercel tags (#11291)
• feat(node): Add scope to ANR events (#11256)
• feat(node): Do not include prismaIntegration by default (#11265)
• feat(node): Ensure tracePropagationTargets are respected (#11285)
• feat(node): Simplify SentrySpanProcessor (#11273)
• feat(profiling): Use OTEL powered node package (#11239)
• feat(utils): Allow text encoder/decoder polyfill from global SENTRY (#11283)
• fix(nextjs): Show misconfiguration warning (no instrumentation.ts) (#11266)
• fix(node): Add logs when node-fetch cannot be instrumented (#11289)
• fix(node): Skip capturing Hapi Boom error responses. (#11151)
• fix(node): Use suppressTracing to avoid capturing otel spans (#11288)
• fix(opentelemetry): Do not stomp span status when startSpan callback throws (#11170)