@sentry/utils

Important Changes

• nuxt: Add option autoInjectServerSentry (no default import())

  Using the dynamic import() as the default behavior for initializing the SDK on the server-side did not work for every project.
  The default behavior of the SDK has been changed, and you now need to use the --import flag to initialize Sentry on the server-side to leverage full functionality.

  Example with --import:

  node --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs

  In case you are not able to use the --import flag, you can enable auto-injecting Sentry in the nuxt.config.ts (comes with limitations):

  sentry: {
    autoInjectServerSentry: 'top-level-import', // or 'experimental_dynamic-import'
  },

• browser: Adds LaunchDarkly and OpenFeature integrations

  Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:

  import * as Sentry from '@sentry/browser';
  
  Sentry.init({
    integrations: [
      // Track LaunchDarkly feature flags
      Sentry.launchDarklyIntegration(),
      // Track OpenFeature feature flags
      Sentry.openFeatureIntegration(),
    ],
  });

  • Read more about the Feature Flags feature in Sentry.

  • Read more about the LaunchDarkly SDK Integration.

  • Read more about the OpenFeature SDK Integration.

• browser: Add featureFlagsIntegration for custom tracking of flag evaluations

  Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:

  import * as Sentry from '@sentry/browser';
  
  const featureFlagsIntegrationInstance = Sentry.featureFlagsIntegration();
  
  Sentry.init({
    // Initialize the SDK with the feature flag integration
    integrations: [featureFlagsIntegrationInstance],
  });
  
  // Manually track a feature flag
  featureFlagsIntegrationInstance.addFeatureFlag('my-feature', true);

• astro: Add Astro 5 support

  With this release, the Sentry Astro SDK officially supports Astro 5.

Deprecations

• deprecated

  nextjs: Deprecate typedef for hideSourceMaps

  The functionality of hideSourceMaps was removed in version 8 but was forgotten to be deprecated and removed.
  It will be completely removed in the next major version.

• deprecated

  core: Deprecate APIs around RequestSessions

  The APIs around RequestSessions are mostly used internally.
  Going forward the SDK will not expose concepts around RequestSessions.
  Instead, functionality around server-side Release Health will be managed in integrations.

Other Changes

• browser: Add browserSessionIntegration

• core: Add raw_security envelope types

• nestjs: Add fastify support

• node: Add @vercel/ai instrumentation

• node: Add disableAnrDetectionForCallback function

• node: Add trackIncomingRequestsAsSessions option to http integration

• nuxt: Add option autoInjectServerSentry (no default import())

• nuxt: Add warning when Netlify or Vercel build is discovered

• nuxt: Improve serverless event flushing and scope isolation

• opentelemetry: Stop looking at propagation context for span creation

• opentelemetry: Update OpenTelemetry dependencies to ^1.29.0

• opentelemetry: Update OpenTelemetry dependencies to 1.28.0

• replay: Upgrade rrweb packages to 2.30.0

• core: Decode filename and module stack frame properties in Node stack parser

• core: Filter out unactionable CEFSharp promise rejection error by default

• nextjs: Don't show warning about devtool option

• nextjs: Only apply tracing metadata to data fetcher data when data is an object

• node: Guard against invalid maxSpanWaitDuration values

• react: Match routes with parseSearch option in TanStack Router instrumentation

• sveltekit: Fix git SHA not being picked up for release

• types: Fix generic exports with default

Work in this release was contributed by @lsmurray. Thank you for your contribution!

Bundle size