@sentry-internal/replay-canvas
Advanced tools
Changelog
8.0.0-alpha.4
This is the fourth Alpha release of the v8 cycle, 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.
The minimum Node version required for the SDK is now 14.18.0
.
@sentry/google-cloud-serverless
(#11065)@sentry/serverless
is no longer published, and is replaced by two new packages: @sentry/google-cloud-serverless
and
@sentry/aws-serverless
. These packages are now the recommended way to instrument serverless functions. See the
migration guide for more details.
The Browser SDK and CDN bundles now emits ES2017 compatible code and drops support for IE11. This also means that the
Browser SDKs (@sentry/browser
, @sentry/react
, @sentry/vue
, etc.) requires the fetch API to be available in the
environment. If you need to support older browsers, please transpile your code to ES5 using babel or similar and add
required polyfills.
New minimum supported browsers:
startTransaction
export (#11015)unmask
and unblock
(#11049)replaySession
and errorSampleRates
(#11045)spanRecorder
and all related code (#10977)origin
field on span start options (#11058)startSpan
options (#11054)startTransaction
& finishTransaction
hooks (#11008)sentry
field in Next.js config as a means of configuration (#10839)startChild
deprecations (#10956)getRootSpan()
does not rely on transaction (#10979)getSpanDescendants()
everywhere (#10924)transactionName
when route is resolved (#11043)name
parameter (#11057)@sentry/astro
to use OpenTelemetry (#10960)HttpContext
integration class (#10987)scope.transactionName
from root spans (#10991)startIdleSpan
(#10934)__SENTRY__
singleton (#11034)__SENTRY__
(#11074)continueTrace
to be callback-only (#11044)spanToJSON
to handle OTEL spans (#10922)tunnelRoute
option (#10959)setupFastifyErrorHandler
utility (#11061)getRootSpan
functionality (#11004)transactionName
in React Router instrumentations (#11048)unstable_sentryVitePluginOptions
for full Vite plugin customization (#10930)createReduxEnhancer
on server (#11005)handled
value in ErrorBoundary depending on fallback (#10989)addScopeListener
to Scope
interface (#10952)AttachmentType
and use for envelope attachment_type
property (#10946)allowSyntheticDefaultImports
(#11073)startChild
(#11056)scope.transactionName
on pageload and navigation span creation (#10992)startChild()
(#11047)http
& undici
(#11055)Work in this release contributed by @MFoster and @jessezhang91. Thank you for your contributions!
Changelog
8.0.0-alpha.3
This alpha was released in an incomplete state. We recommend skipping this release and using the 8.0.0-alpha.4
release
instead.
Changelog
8.0.0-alpha.2
This alpha release fixes a build problem that prevented 8.0.0-alpha.1 from being properly released.
@sentry/opentelemetry-node
package (#10906)The @sentry/opentelemetry-node
package has been removed. Instead, you can either use @sentry/node
with built-in
OpenTelemetry support, or use @sentry/opentelemetry
to manually connect Sentry with OpenTelemetry.
startSpan
options (#10825)skipOpenTelemetrySetup
(#10907)inspector
(#10910)Work in this release contributed by @harish-talview & @bfontaine. Thank you for your contributions!
Changelog
8.0.0-alpha.1
This is the first Alpha release of the v8 cycle, 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.
- feat(node): Make @sentry/node
powered by OpenTelemetry (#10762)
The biggest change is the switch to use OpenTelemetry under the hood in @sentry/node
. This brings with it a variety of
changes:
autoDiscoverNodePerformanceMonitoringIntegrations()
anymore.Sentry.init()
before you import any other packages. Otherwise, the packages cannot be
instrumented:const Sentry = require('@sentry/node');
Sentry.init({
dsn: '...',
// ... other config here
});
// now require other things below this!
const http = require('http');
const express = require('express');
// ....
startTransaction
and span.startChild()
are no longer supported. This is due to the underlying change to
OpenTelemetry powered performance instrumentation. See
docs on the new performance APIs for details.Related changes:
defaultStackParser
& getSentryRelease
(#10722)errorHandler
(#10728)forceTransaction
in OTEL (#10807)isInitialized
(#10607)errorHandler
to expressErrorHandler
(#10746)- feat: Remove @sentry/integrations
package (#10799)
This package is no longer published. You can instead import these pluggable integrations directly from your SDK package
(e.g. @sentry/browser
or @sentry/react
).
- feat: Remove @sentry/hub
package (#10783)
This package is no longer published. You can instead import directly from your SDK package (e.g. @sentry/react
or
@sentry/node
).
- feat(v8): Remove @sentry/tracing (#10625)
This package is no longer published. You can instead import directly from your SDK package (e.g. @sentry/react
or
@sentry/node
).
- feat: Set required node version to >=14.8.0 for all packages (#10834)
The minimum required node version is now 14.8+. If you need support for older node versions, you can stay on the v7 branch.
- Removed class-based integrations
We have removed most of the deprecated class-based integrations. Instead, you can use the functional styles:
import * as Sentry from '@sentry/browser';
// v7
Sentry.init({
integrations: [new Sentry.BrowserTracing()],
});
// v8
Sentry.init({
integrations: [new Sentry.browserTracingIntegration()],
});
BrowserTracing
(#10653)- feat(v8/browser): Remove XHR transport (#10703)
We have removed the XHR transport, and are instead using the fetch-based transport now by default. This means that if you are using Sentry in a browser environment without fetch, you'll need to either provide a fetch polyfill, or provide a custom transport to Sentry.
- feat(sveltekit): Update @sentry/vite-plugin
to 2.x and adjust options API (#10813)
We have updated @sentry/sveltekit
to use the latest version of @sentry/vite-plugin
, which lead to changes in
configuration options.
withActiveSpan
is exported everywhere (#10878)null
to withActiveSpan
(#10717)hub
from global, hub.run
& hub utilities (#10718)getIsolationScope
and getGlobalScope
(#10658)setXXX
methods set on isolation scope (#10678)addBreadcrumb
write to the isolation scope instead of current scope (#10586)addEventProcessor
to add to isolation scope (#10606)Sentry.addBreadcrumb
to skip hub (#10601)TextEncoder
and TextDecoder
(#10701)captureConsoleIntegration
(#10744)BaseClient
(#10789)exports
field to package.json
(#10569)captureContext
function (#10735)webpack://
prefix more broadly from source map sources
field (#10642)worker_threads
and fix node v14 types (#10791)null
and undefined
(#10821)?
for anonymous function name (#10732)on
and emit
required on client (#10603)Span
class to SentrySpan
(#10687)captureXXX
methods (#10688)number
as span traceFlag
(#10855)status
field from Span (#10856)@remix-run/router
a dependency. (#10479)beforeAddBreadcrumb
hook instead of scope listener (#10600)We have also removed or updated a variety of deprecated APIs.
extractTraceparentData
export (#10559)span.isSuccess
method (#10699)traceHeaders
method (#10776)_eventFromIncompleteOnError
usage (#10553)browserApiErrorsIntegration
(#10755)Span
interface (#10854)setupOnce
optional in integrations (#10729)makeMain
usage (#10713)scope.applyToEvent()
method (#10842)lastEventId
(#10585)reuseExisting
option for ACS (#10645)tracingOrigins
options (#10614)showReportDialog
APIs (#10609)A full list of changes in the 7.x
release of the SDK can be found in the 7.x Changelog.
A full list of changes in the 6.x
release of the SDK can be found in the 6.x Changelog.
A full list of changes in the 5.x
release of the SDK can be found in the 5.x Changelog.
A full list of changes in the 4.x
release of the SDK can be found in the 4.x Changelog.