@sentry-internal/replay
Advanced tools
Changelog
8.40.0
feat(angular): Support Angular 19 (#14398)
The @sentry/angular
SDK can now be used with Angular 19. If you're upgrading to the new Angular version, you might want to migrate from the now deprecated APP_INITIALIZER
token to provideAppInitializer
.
In this case, change the Sentry TraceService
initialization in app.config.ts
:
// Angular 18
export const appConfig: ApplicationConfig = {
providers: [
// other providers
{
provide: TraceService,
deps: [Router],
},
{
provide: APP_INITIALIZER,
useFactory: () => () => {},
deps: [TraceService],
multi: true,
},
],
};
// Angular 19
export const appConfig: ApplicationConfig = {
providers: [
// other providers
{
provide: TraceService,
deps: [Router],
},
provideAppInitializer(() => {
inject(TraceService);
}),
],
};
feat(core): Deprecate debugIntegration
and sessionTimingIntegration
(#14363)
The debugIntegration
was deprecated and will be removed in the next major version of the SDK.
To log outgoing events, use Hook Options (beforeSend
, beforeSendTransaction
, ...).
The sessionTimingIntegration
was deprecated and will be removed in the next major version of the SDK.
To capture session durations alongside events, use Context (Sentry.setContext()
).
feat(nestjs): Deprecate @WithSentry
in favor of @SentryExceptionCaptured
(#14323)
The @WithSentry
decorator was deprecated. Use @SentryExceptionCaptured
instead. This is a simple renaming and functionality stays identical.
feat(nestjs): Deprecate SentryTracingInterceptor
, SentryService
, SentryGlobalGenericFilter
, SentryGlobalGraphQLFilter
(#14371)
The SentryTracingInterceptor
was deprecated. If you are using @sentry/nestjs
you can safely remove any references to the SentryTracingInterceptor
. If you are using another package migrate to @sentry/nestjs
and remove the SentryTracingInterceptor
afterwards.
The SentryService
was deprecated and its functionality was added to Sentry.init
. If you are using @sentry/nestjs
you can safely remove any references to the SentryService
. If you are using another package migrate to @sentry/nestjs
and remove the SentryService
afterwards.
The SentryGlobalGenericFilter
was deprecated. Use the SentryGlobalFilter
instead which is a drop-in replacement.
The SentryGlobalGraphQLFilter
was deprecated. Use the SentryGlobalFilter
instead which is a drop-in replacement.
feat(node): Deprecate nestIntegration
and setupNestErrorHandler
in favor of using @sentry/nestjs
(#14374)
The nestIntegration
and setupNestErrorHandler
functions from @sentry/node
were deprecated and will be removed in the next major version of the SDK. If you're using @sentry/node
in a NestJS application, we recommend switching to our new dedicated @sentry/nestjs
package.
normalizedRequest
on sdkProcessingMetadata
is merged (#14315)@sentry/utils
into @sentry/core
(#14382)__self
and __source
attributes on feedback nodes (#14356)Changelog
8.39.0
The @sentry/nestjs
SDK will now capture performance data for NestJS Events (@nestjs/event-emitter
)
@SentryExceptionCaptured
for @WithSentry
(#14322)SentryService
behaviour into @sentry/nestjs
SDK init()
(#14321)SentryGlobalFilter
(#14320)childProcessIntegration
for processThreadBreadcrumbIntegration
and deprecate it (#14334)_sentryModuleMetadata
is not mangled (#14344)sentry.source
attribute to custom
when calling span.updateName
on SentrySpan
(#14251)Request
type in favor of RequestEventData
(#14317)transaction
in requestDataIntegration
(#14306)Changelog
8.38.0
knex
integration (#13526)tedious
integration (#13486)debug_meta
with ANR events (#14203)Work in this release was contributed by @grahamhency, @Zen-cronic, @gilisho and @phuctm97. Thank you for your contributions!
Changelog
8.37.0
piniaIntegration
(#14138)The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, add the piniaIntegration
to your client config:
// sentry.client.config.ts
import { usePinia } from '#imports';
Sentry.init({
integrations: [
Sentry.piniaIntegration(usePinia(), {
/* optional Pinia plugin options */
}),
],
});
The Sentry Metrics beta has ended in favour of revisiting metrics in another form at a later date.
This new approach will include different APIs, making the current metrics API unnecessary. This release deprecates the metrics API with the plan to remove in the next SDK major version. If you currently use the metrics API in your code, you can safely continue to do so but sent data will no longer be processed by Sentry.
Learn more about the end of the Metrics beta.
http.response_delivery_type
attribute to resource spans (#14056)skipBrowserExtensionCheck
escape hatch option (#14147)asyncFunctionReExports
to define re-exported server functions (#14104)piniaIntegration
(#14138)maybeInstrument
(#14140)modulesIntegration
does not crash esm apps (#14169)Work in this release was contributed by @rexxars. Thank you for your contribution!
Changelog
8.36.0
With this release, the Sentry Next.js, and Cloudflare SDKs will now capture performance data based on OpenTelemetry. Some exceptions apply in cases where Next.js captures inaccurate data itself.
NOTE: You may experience minor differences in transaction names in Sentry.
Most importantly transactions for serverside pages router invocations will now be named GET /[param]/my/route
instead of /[param]/my/route
.
This means that those transactions are now better aligned with the OpenTelemetry semantic conventions.
child_process
and worker_thread
(#13896).mjs
entry files in rollup (#14060)onError
callback (#14002)