@sentry/react - npm Package Versions

8.37.1

• feat(deps): Bump @opentelemetry/instrumentation from 0.53.0 to 0.54.0 for @sentry/opentelemetry (#14187)

8.37.0

Important Changes

• feat(nuxt): Add 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 */
    }),
  ],
});

• feat: Deprecate metrics API (#14157)

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.

Other Changes

• feat(browser): Add http.response_delivery_type attribute to resource spans (#14056)
• feat(browser): Add skipBrowserExtensionCheck escape hatch option (#14147)
• feat(deps): Bump @opentelemetry/instrumentation from 0.53.0 to 0.54.0 (#14174)
• feat(deps): Bump @opentelemetry/instrumentation-fastify from 0.40.0 to 0.41.0 (#14175)
• feat(deps): Bump @opentelemetry/instrumentation-graphql from 0.43.0 to 0.44.0 (#14173)
• feat(deps): Bump @opentelemetry/instrumentation-mongodb from 0.47.0 to 0.48.0 (#14171)
• feat(deps): Bump @opentelemetry/propagator-aws-xray from 1.25.1 to 1.26.0 (#14172)
• feat(nuxt): Add asyncFunctionReExports to define re-exported server functions (#14104)
• feat(nuxt): Add piniaIntegration (#14138)
• fix(browser): Avoid recording long task spans starting before their parent span (#14183)
• fix(core): Ensure errors thrown in async cron jobs bubble up (#14182)
• fix(core): Silently fail maybeInstrument (#14140)
• fix(nextjs): Resolve path for dynamic webpack import (#13751)
• fix(node): Make sure modulesIntegration does not crash esm apps (#14169)

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

8.36.0

Important Changes

• feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)

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.

Other Changes

• deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
• feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
• feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
• feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
• feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
• feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
• feat(nextjs): Add method and url to route handler request data (#14084)
• feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
• fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
• fix(nextjs): Await flush in api handlers (#14023)
• fix(nextjs): Don't leak webpack types into exports (#14116)
• fix(nextjs): Fix matching logic for file convention type for root level components (#14038)
• fix(nextjs): Respect directives in value injection loader (#14083)
• fix(nuxt): Only wrap .mjs entry files in rollup (#14060)
• fix(nuxt): Re-export all exported bindings (#14086)
• fix(nuxt): Server-side setup in readme (#14049)
• fix(profiling-node): Always warn when running on incompatible major version of Node.js (#14043)
• fix(replay): Fix onError callback (#14002)
• perf(otel): Only calculate current timestamp once (#14094)
• test(browser-integration): Add sentry DSN route handler by default (#14095)

8.35.0

Beta release of the official Nuxt Sentry SDK

This release marks the beta release of the @sentry/nuxt Sentry SDK. For details on how to use it, check out the Sentry Nuxt SDK README. Please reach out on GitHub if you have any feedback or concerns.

• feat(nuxt): Make dynamic import() wrapping default (#13958) (BREAKING)
• feat(nuxt): Add Rollup plugin to wrap server entry with import() (#13945)

It is no longer required to add a Node --import flag. Please update your start command to avoid initializing Sentry twice (BREAKING CHANGE). The SDK will now apply modifications during the build of your application to allow for patching of libraries during runtime. If run into issues with this change, you can disable this behavior in your nuxt.config.ts and use the --import flag instead:

sentry: {
  dynamicImportForServerEntry: false;
}

• feat(nuxt): Respect user-provided source map generation settings (#14020)

We now require you to explicitly enable sourcemaps for the clientside so that Sentry can un-minify your errors. We made this change so source maps aren't accidentally leaked to the public. Enable source maps on the client as follows:

export default defineNuxtConfig({
  sourcemap: {
    client: true,
  },
});

• feat(nuxt): Log server instrumentation might not work in dev (#14021)
• feat(nuxt): Add Http responseHook with waitUntil (#13986)

Important Changes

• feat(vue): Add Pinia plugin (#13841)

Support for Pinia is added in this release for @sentry/vue. To capture Pinia state data, add createSentryPiniaPlugin() to your Pinia store:

import { createPinia } from 'pinia';
import { createSentryPiniaPlugin } from '@sentry/vue';

const pinia = createPinia();

pinia.use(createSentryPiniaPlugin());

• feat(node): Implement Sentry-specific http instrumentation (#13763)

This change introduces a new SentryHttpInstrumentation to handle non-span related HTTP instrumentation, allowing it to run side-by-side with OTel's HttpInstrumentation. This improves support for custom OTel setups and avoids conflicts with Sentry's instrumentation. Additionally, the spans: false option is reintroduced for httpIntegration to disable span emission while still allowing custom HttpInstrumentation instances (httpIntegration({ spans: false })).

• feat(core): Make stream instrumentation opt-in (#13951)

This change adds a new option trackFetchStreamPerformance to the browser tracing integration. Only when set to true, Sentry will instrument streams via fetch.

Other Changes

• feat(node): Expose suppressTracing API (#13875)
• feat(replay): Do not log "timeout while trying to read resp body" as exception (#13965)
• chore(node): Bump @opentelemetry/instrumentation-express to 0.43.0 (#13948)
• chore(node): Bump @opentelemetry/instrumentation-fastify to 0.40.0 (#13983)
• fix: Ensure type for init is correct in meta frameworks (#13938)
• fix(core): .set the sentry-trace header instead of .appending in fetch instrumentation (#13907)
• fix(module): keep version for node ESM package (#13922)
• fix(node): Ensure ignoreOutgoingRequests of httpIntegration applies to breadcrumbs (#13970)
• fix(replay): Fix onError sampling when loading an expired buffered session (#13962)
• fix(replay): Ignore older performance entries when starting manually (#13969)
• perf(node): Truncate breadcrumb messages created by console integration (#14006)

Work in this release was contributed by @ZakrepaShe and @zhiyan114. Thank you for your contributions!