@sentry/integrations
Advanced tools
Changelog
7.109.0
This release deprecates some exports from the @sentry/replay
package. These exports have been moved to the browser SDK
(or related framework SDKs like @sentry/react
).
rrweb
to 2.12.0 (#11317)@sentry/replay
exports (#11242)Work in this release contributed by @soerface. Thank you for your contribution!
Changelog
7.108.0
This release fixes issues with Time to First Byte (TTFB) calculation in the SDK that was introduced with 7.95.0
. It
also fixes some bugs with Interaction to First Paint (INP) instrumentation. This may impact your Sentry Performance
Score calculation.
ResizeObserver
and googletag
default filters (#11210)cron
(#11225)sampled
type on Transaction
(#11146)Work in this release contributed by @quisido and @joshkel. Thank you for your contributions!
Changelog
7.107.0
This release fixes issues with INP instrumentation with the Next.js SDK and adds support for the enableInp
option in
the deprecated BrowserTracing
integration for backwards compatibility.
handled
value in ErrorBoundary depending on fallback [v7] (#11037)Changelog
7.106.1
createReduxEnhancer
on server (#11010)Changelog
7.106.0
tunnelRoute
option (#10958)setTransactionName
global
(#10925)AttachmentType
and use for envelope attachment_type
property (#10946)Work in this release contributed by @jessezhang91 and @bfontaine. Thank you for your contributions!
Changelog
7.105.0
withActiveSpan
is exported everywhere (#10877)You can use the withActiveSpan
method to ensure a certain span is the active span in a given callback. This can be
used to create a span as a child of a specific span with the startSpan
API methods:
const parentSpan = Sentry.startInactiveSpan({ name: 'parent' });
if (parentSpan) {
withActiveSpan(parentSpan, () => {
// This will be a direct child of parentSpan
const childSpan = Sentry.startInactiveSpan({ name: 'child' });
});
}
Changelog
7.104.0
This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support
is released with the upcoming 24.3.0
release of self-hosted.
To opt-in to this feature, you can use the enableInp
option in the browserTracingIntegration
:
Sentry.init({
integrations: [
Sentry.browserTracingIntegration({
enableInp: true,
});
]
})
nodeProfilingIntegration
(#10864)errorHandler
for replayCanvas integration (#10796)Changelog
7.103.0
forceTransaction
to startSpan()
APIs (#10819)You can now pass forceTransaction: true
to startSpan()
, startSpanManual()
and startInactiveSpan()
. This allows
you to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to
the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if
possible, ensuring it shows up as a transaction throughout the system.
Please note that setting this to true
does not guarantee that this will be sent as a transaction, but that the SDK
will try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it
in the Sentry UI.
Changelog
7.102.1
window.location
(#10659)@remix-run/router
a dependency (v7) (#10779)Changelog
7.102.0
captureContext
function (#10737)