@sentry/ember

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)

• nuxt: Add Rollup plugin to wrap server entry with import()

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;
}

• nuxt: Respect user-provided source map generation settings

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

• nuxt: Log server instrumentation might not work in dev

• nuxt: Add Http responseHook with waitUntil

Important Changes

• vue: Add Pinia plugin

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

• node: Implement Sentry-specific http instrumentation

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

• core: Make stream instrumentation opt-in

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

• node: Expose suppressTracing API

• replay: Do not log "timeout while trying to read resp body" as exception

• Ensure type for init is correct in meta frameworks

• core: .set the sentry-trace header instead of .appending in fetch instrumentation

• module: Keep version for node ESM package

• node: Ensure ignoreOutgoingRequests of httpIntegration applies to breadcrumbs

• replay: Fix onError sampling when loading an expired buffered session

• replay: Ignore older performance entries when starting manually

• node: Truncate breadcrumb messages created by console integration

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

Bundle size