@sentry/types
Advanced tools
Changelog
8.35.0
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.
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;
}
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,
},
});
responseHook
with waitUntil
(#13986)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());
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 })
).
This change adds a new option trackFetchStreamPerformance
to the browser tracing integration. Only when set to true
,
Sentry will instrument streams via fetch.
suppressTracing
API (#13875)@opentelemetry/instrumentation-express
to 0.43.0
(#13948)@opentelemetry/instrumentation-fastify
to 0.40.0
(#13983)init
is correct in meta frameworks
(#13938).set
the sentry-trace
header instead of .append
ing in fetch instrumentation
(#13907)ignoreOutgoingRequests
of httpIntegration
applies to breadcrumbs
(#13970)Work in this release was contributed by @ZakrepaShe and @zhiyan114. Thank you for your contributions!
Changelog
8.34.0
Relevant for users of the @sentry/nextjs
package: If you have previously configured a
SENTRY_IGNORE_API_RESOLUTION_ERROR
environment variable, it is now safe to unset it.
getReplay
in replay CDN bundles
(#13881)globalThis
(#13788)requestAsyncStorageShim.js
template file
(#13928)_not-found
spans for all HTTP methods
(#13906)dataloader
instrumentation from default integrations
(#13873)replay_id
is removed from frozen DSC when stopped
(#13893)sendBufferedReplayOrFlush
to prevent cycles
(#13900)wrapServerRouteWithSentry
to respect ParamMatchers
(#13390)vercelWaitUntil
to utils (#13891)Work in this release was contributed by @trzeciak, @gurpreetatwal, @ykzts and @lizhiyao. Thank you for your contributions!
Changelog
8.33.0
headers()
, params
, searchParams
)
(#13828)Adds support for new dynamic Next.js APIs.
lru-memoizer
instrumentation
(#13796)Adds integration for lru-memoizer using @opentelemetry/instrumentation-lru-memoizer.
unstable_sentryBundlerPluginOptions
to module options
(#13811)Allows passing other options from the bundler plugins (vite and rollup) to Nuxt module options.
wrap()
only returns functions
(#13838)getTraceData
and getTraceMetaTags
if SDK is disabled
(#13760)Work in this release was contributed by @joshuajaco. Thank you for your contribution!