@sentry/utils

Important Changes

• angular: Support Angular 19

  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);
      }),
    ],
  };

• deprecated

  core: Deprecate debugIntegration and sessionTimingIntegration

  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()).

• deprecated

  nestjs: Deprecate @WithSentry in favor of @SentryExceptionCaptured

  The @WithSentry decorator was deprecated. Use @SentryExceptionCaptured instead. This is a simple renaming and functionality stays identical.

• deprecated

  nestjs: Deprecate SentryTracingInterceptor, SentryService, SentryGlobalGenericFilter, SentryGlobalGraphQLFilter

  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.

• deprecated

  node: Deprecate nestIntegration and setupNestErrorHandler in favor of using @sentry/nestjs

  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.

Other Changes

• browser: Send additional LCP timing info

• replay: Clear event buffer when full and in buffer mode

• core: Ensure normalizedRequest on sdkProcessingMetadata is merged

• core: Hoist everything from @sentry/utils into @sentry/core

• core: Do not throw when trying to fill readonly properties

• feedback: Fix __self and __source attributes on feedback nodes

• feedback: Fix non-wrapping form title

• nextjs: Update check for not found navigation error

Bundle size