@sentry/core
Advanced tools
Changelog
8.39.0
The @sentry/nestjs
SDK will now capture performance data for NestJS Events (@nestjs/event-emitter
)
@SentryExceptionCaptured
for @WithSentry
(#14322)SentryService
behaviour into @sentry/nestjs
SDK init()
(#14321)SentryGlobalFilter
(#14320)childProcessIntegration
for processThreadBreadcrumbIntegration
and deprecate it (#14334)_sentryModuleMetadata
is not mangled (#14344)sentry.source
attribute to custom
when calling span.updateName
on SentrySpan
(#14251)Request
type in favor of RequestEventData
(#14317)transaction
in requestDataIntegration
(#14306)Changelog
8.38.0
knex
integration (#13526)tedious
integration (#13486)debug_meta
with ANR events (#14203)Work in this release was contributed by @grahamhency, @Zen-cronic, @gilisho and @phuctm97. Thank you for your contributions!
Changelog
8.37.0
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 */
}),
],
});
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.
http.response_delivery_type
attribute to resource spans (#14056)skipBrowserExtensionCheck
escape hatch option (#14147)asyncFunctionReExports
to define re-exported server functions (#14104)piniaIntegration
(#14138)maybeInstrument
(#14140)modulesIntegration
does not crash esm apps (#14169)Work in this release was contributed by @rexxars. Thank you for your contribution!
Changelog
8.36.0
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.
child_process
and worker_thread
(#13896).mjs
entry files in rollup (#14060)onError
callback (#14002)