@sentry-internal/feedback
Advanced tools
Changelog
9.0.0
Version 9.0.0
marks a release of the Sentry JavaScript SDKs that contains breaking changes.
The goal of this release is to trim down on unused and potentially confusing APIs, prepare the SDKs for future framework versions to build deeper instrumentation, and remove old polyfills to reduce the packages' size.
Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 8 to version 9. Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/
A comprehensive migration guide outlining all changes for all the frameworks can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md
~5.0.0
(#14758)nitro-utils
package (#14998)sendDefaultPii: true
(#15084)autoSessionTracking
option (#14802)enableTracing
(#15078)getCurrentHub()
, Hub
, and getCurrentHubShim()
(#15122)spanId
from propagation context (#14733)>=18
as minimum supported version (#14749)captureUserFeedback
method (#14820)normalizedRequest
to samplingContext
(#14902)beforeSendSpan
and disallow returning null
(#14831)BAGGAGE_HEADER_NAME
export (#14785)TransactionNamingScheme
type (#14865)addOpenTelemetryInstrumentation
method (#14792)arrayify
method (#14782)debugIntegration
and sessionTimingIntegration
(#14747)flatten
method (#14784)getDomElement
method (#14797)makeFifoCache
method (#14786)memoBuilder
export & WeakSet
fallback (#14859)transactionContext
from samplingContext
(#14904)urlEncode
method (#14783)Request
type (#14858)Client
interface & deprecate BaseClient
(#14800)event
as argument for recordDroppedEvent
(#14999)requestDataIntegration
(#14898)hasTracingEnabled
to consider empty trace config (#14857)requestDataIntegration
handling (#14806)<=3.x
(#15032)nestIntegration
into nest sdk and remove setupNestErrorHandler
(#14751)@WithSentry
decorator (#14762)SentryService
(#14759)experimental_captureRequestError
(#14607)processThreadBreadcrumbIntegration
(#14666)registerEsmLoaderHooks
(#15002)1.63.0
(#15030)getNumberOfUrlSegments
method (#14744)ErrorBoundary
componentStack
type (#14742)autoInstrumentRemix
option (#15074)--import
setup and add autoInjectServerSentry
(#14862)sentrySolidStartVite
(#15143)fetchProxyScriptNonce
option (#15123)@sentry/utils
package (#14830)vueIntegration
's tracingOptions
option (#14856)"update"
spans for component tracking by default (#14602)vercelAIIntegration
to VercelAI
(#15298)logError
from vueIntegration
(#14958)ReportDialogOptions
(#14861)captureConsoleIntegration
as handled: true
by default (#14734)shutdownTimeout
option type from core to node (#15217)Scope
type interface in favor of using Scope
class (#14721)import-in-the-middle
to 1.12.0
(#14796)SentryNodeServerlessSDKv9
(#14927)user.ip_address
explicitly to {{auto}}
(#15008)inheritOrSampleWith
helper to traceSampler
(#15277)hasTracingEnabled
to hasSpansEnabled
(#15309)SpanJSON
type (#14693)@sentry/deno
(#15014)deno.land
(#15016)SentryTracingInterceptor
, SentryGlobalGraphQLFilter
, SentryGlobalGenericFilter
(#14761)sourcemaps.disable
to webpack plugin (#15109)processSessionIntegration
(#15081)vercelAIIntegration
export (#15318)worker_threads
(#15105)silent
, errorHandler
, release
to SourceMapsOptions
(#15246)@sentry-internal/node-cpu-profiler
(#15208)autoInjectServerSentry: 'experimental_dynamic-import
(#14863)__esModule
properties in CJS modules when there is a default export (#15018)parentSampleRate
to tracesSampler
(#15024)browserPerformanceTimeOrigin
side-effects (#14025)startSpanManual
(#14901)startSpan
(#14900)sendDefaultPii
for IP collection in requestDataIntegration
(#15125)waitUntil
in captureRequestError
(#15146)__span
property into breadcrumbs (#14798)httpIntegration
propagates traces (#15233)release
from ANR sessions (#15138)browserTracingIntegration
(#14959)supportsHistory
check & history usage (#14696)Work in this release was contributed by @aloisklink, @arturovt, @aryanvdesh, @benjick, @chris-basebone, @davidturissini, @GrizliK1988, @jahands, @jrandolf, @kunal-511, @maximepvrt, @maxmaxme, @mstrokin, @nathankleyn, @nwalters512, @tannerlinsley, @tjhiggins, and @Zen-cronic. Thank you for your contributions!
Changelog
9.0.0-alpha.2
This is an alpha release of the upcoming major release of version 9. This release does not yet entail a comprehensive changelog as version 9 is not yet stable.
For this release's iteration of the migration guide, see the Migration Guide as per 9.0.0-alpha.2
.
Please note that the migration guide is work in progress and subject to change.
Changelog
9.0.0-alpha.1
This is an alpha release of the upcoming major release of version 9. This release does not yet entail a comprehensive changelog as version 9 is not yet stable.
For this release's iteration of the migration guide, see the Migration Guide as per 9.0.0-alpha.1
.
Please note that the migration guide is work in progress and subject to change.
Changelog
8.53.0
url
to SourcemapsUploadOptions
(#15202)fromLocation
can be undefined in Tanstack Router Instrumentation (#15237)Work in this release was contributed by @tannerlinsley. Thank you for your contribution!
Changelog
8.52.1
this.name
to new.target.prototype.constructor.name
(#15222)Work in this release was contributed by @Zen-cronic. Thank you for your contribution!
Changelog
8.52.0
withSentry
wrapper for SolidStart config (#15135)To enable the SolidStart SDK, wrap your SolidStart Config with withSentry
. The sentrySolidStartVite
plugin is now automatically
added by withSentry
and you can pass the Sentry build-time options like this:
import { defineConfig } from '@solidjs/start/config';
import { withSentry } from '@sentry/solidstart';
export default defineConfig(
withSentry(
{
/* Your SolidStart config options... */
},
{
// Options for setting up source maps
org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,
authToken: process.env.SENTRY_AUTH_TOKEN,
},
),
);
With the withSentry
wrapper, the Sentry server config should not be added to the public
directory anymore.
Add the Sentry server config in src/instrument.server.ts
. Then, the server config will be placed inside the server build output as instrument.server.mjs
.
Now, there are two options to set up the SDK:
--import
CLI flag to the start command like this (path depends on your server setup):
node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
autoInjectServerSentry: 'top-level-import'
and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)
withSentry(
{
/* Your SolidStart config options... */
},
{
// Optional: Install Sentry with a top-level import
autoInjectServerSentry: 'top-level-import',
},
);
Bun.serve
survives a server reload (#15157)module
into loadModule
(#15139) (#15166)Work in this release was contributed by @jahands, @jrandolf, and @nathankleyn. Thank you for your contributions!
Changelog
8.51.0
feat(v8/node): Add prismaInstrumentation
option to Prisma integration as escape hatch for all Prisma versions (#15128)
This release adds a compatibility API to add support for Prisma version 6. To capture performance data for Prisma version 6:
Install the @prisma/instrumentation
package on version 6.
Pass a new PrismaInstrumentation()
instance as exported from @prisma/instrumentation
to the prismaInstrumentation
option:
import { PrismaInstrumentation } from '@prisma/instrumentation';
Sentry.init({
integrations: [
prismaIntegration({
// Override the default instrumentation that Sentry uses
prismaInstrumentation: new PrismaInstrumentation(),
}),
],
});
The passed instrumentation instance will override the default instrumentation instance the integration would use, while the prismaIntegration
will still ensure data compatibility for the various Prisma versions.
Remove the previewFeatures = ["tracing"]
option from the client generator block of your Prisma schema.
multiplexedtransport.js
CDN bundle (#15046)fetchProxyScriptNonce
option (#15011)fatal
events should set session as crashed (#15073)Work in this release was contributed by @tjhiggins, and @nwalters512. Thank you for your contributions!
Changelog
9.0.0-alpha.0
This is an alpha release of the upcoming major release of version 9. This release does not yet entail a comprehensive changelog as version 9 is not yet stable.
For this release's iteration of the migration guide, see the Migration Guide as per 9.0.0-alpha.0
.
Please note that the migration guide is work in progress and subject to change.