@sentry-internal/replay
Advanced tools
Changelog
Important Changes since v8.0.0-alpha.9
Because execution context isolation in browser environments does not work reliably, we deciced to keep a flat span hierarchy by default in v8.
addTracingExtensions
(#11579)Instead of calling Sentry.addTracingExtensions()
if you want to use performance in a browser SDK without using
browserTracingIntegration()
, you should now call Sentry.registerSpanErrorInstrumentation()
.
suppressTracing
(#11468)You can use the new suppressTracing
API to ensure a given callback will not generate any spans:
return Sentry.suppressTracing(() => {
// Ensure this fetch call does not generate a span
return fetch('/my-url');
});
import
and loader
(#11498)We renamed the loader hooks for better clarity:
Changelog
8.0.0-alpha.8
This is a partially broken release and was superseded by version 8.0.0-alpha.9
.
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.
We now use OpenTelemetry under the hood to power performance monitoring and tracing in the Next.js SDK.
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.
scope.setSpan()
and scope.getSpan()
methods (#11051)runtime
and vercel
tags (#11291)prismaIntegration
by default (#11265)tracePropagationTargets
are respected (#11285)SentrySpanProcessor
(#11273)instrumentation.ts
) (#11266)suppressTracing
to avoid capturing otel spans (#11288)startSpan
callback throws (#11170)