chore(deps): update dependency @sentry/react to v9

Renovate Botrequested to merge
renovate/major-sentry-javascript-monorepo into dev

This MR contains the following updates:

Package Type Update Change
@sentry/react (source) peerDependencies major ^7.91.0 -> ^9.0.0

Release Notes

getsentry/sentry-javascript (@​sentry/react)

v9.17.0

Compare Source

  • feat(node): Migrate to @fastify/otel (#​15542)

v9.16.1

Compare Source

  • fix(core): Make sure logs get flushed in server-runtime-client (#​16222)
  • ref(node): Remove vercel flushing code that does nothing (#​16217)

v9.16.0

Compare Source

Important changes
  • feat: Create a Vite plugin that injects sentryConfig into the global config (#​16197)

Add a new plugin makeConfigInjectorPlugin within our existing vite plugin that updates the global vite config with sentry options

  • feat(browser): Add option to sample linked traces consistently (#​16037)

This MR implements consistent sampling across traces as outlined in (#​15754)

  • feat(cloudflare): Add support for durable objects (#​16180)

This MR introduces a new instrumentDurableObjectWithSentry method to the SDK, which instruments durable objects. We capture both traces and errors automatically.

  • feat(node): Add Prisma integration by default (#​16073)

Prisma integration is enabled by default, it should work for both ESM and CJS.

  • feat(react-router): Add client-side router instrumentation (#​16185)

Adds client-side instrumentation for react router's HydratedRouter. To enable it, simply replace browserTracingIntegration() with reactRouterTracingIntegration() in your client-side init call.

  • fix(node): Avoid double-wrapping http module (#​16177)

When running your application in ESM mode, there have been scenarios that resulted in the http/https emitting duplicate spans for incoming requests. This was apparently caused by us double-wrapping the modules for incoming request isolation.

In order to solve this problem, the modules are no longer monkey patched by us for request isolation. Instead, we register diagnosticschannel hooks to handle request isolation now. While this is generally not expected to break anything, there is one tiny change that _may affect you if you have been relying on very specific functionality:

The ignoreOutgoingRequests option of httpIntegration receives the RequestOptions as second argument. This type is not changed, however due to how the wrapping now works, we no longer pass through the full RequestOptions, but re-construct this partially based on the generated request. For the vast majority of cases, this should be fine, but for the sake of completeness, these are the only fields that may be available there going forward - other fields that may have existed before may no longer be set:

ignoreOutgoingRequests(url: string, {
  method: string;
  protocol: string;
  host: string;
  hostname: string; // same as host
  path: string;
  headers: OutgoingHttpHeaders;
})
Other changes
  • feat(cloudflare): Add logs exports (#​16165)
  • feat(vercel-edge): Add logs export (#​16166)
  • feat(cloudflare): Read SENTRY_RELEASE from env (#​16201)
  • feat(node): Drop http.server spans with 404 status by default (#​16205)
  • fix(browser): Respect manually set sentry tracing headers in XHR requests (#​16184)
  • fix(core): Respect manually set sentry tracing headers in fetch calls (#​16183)
  • fix(feedback): Prevent removeFromDom() from throwing (#​16030)
  • fix(node): Use class constructor in docstring for winston transport (#​16167)
  • fix(node): Fix vercel flushing logic & add test for it (#​16208)
  • fix(node): Fix 404 route handling in express 5 (#​16211)
  • fix(logs): Ensure logs can be flushed correctly (#​16216)
  • ref(core): Switch to standardized log envelope (#​16133)

v9.15.0

Compare Source

Important Changes
  • feat: Export wrapMcpServerWithSentry from server packages (#​16127)

Exports the wrapMcpServerWithSentry which is our MCP server instrumentation from all the server packages.

  • feat(core): Associate resource/tool/prompt invocations with request span instead of response span (#​16126)

Adds a best effort mechanism to associate handler spans for resource, tool and prompt with the incoming message requests instead of the outgoing SSE response.

Other Changes
  • fix: Vercel ai ESM patching (#​16152)
  • fix(node): Update version range for module.register (#​16125)
  • fix(react-router): Spread unstable_sentryVitePluginOptions correctly (#​16156)
  • fix(react): Fix Redux integration failing with reducer injection (#​16106)
  • fix(remix): Add ESM-compatible exports (#​16124)
  • fix(remix): Avoid rewrapping root loader. (#​16136)

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

v9.14.0

Compare Source

Important Changes

This MR adds Supabase integration to @sentry/core, allowing automatic instrumentation of Supabase client operations (database queries and authentication) for performance monitoring and error tracking.

  • feat(nestjs): Gracefully handle RPC scenarios in SentryGlobalFilter (#​16066)

This MR adds better RPC exception handling to @sentry/nestjs, preventing application crashes while still capturing errors and warning users when a dedicated filter is needed. The implementation gracefully handles the 'rpc' context type in SentryGlobalFilter to improve reliability in hybrid applications.

  • feat(react-router): Trace propagation (#​16070)

This MR adds trace propagation to @sentry/react-router by providing utilities to inject trace meta tags into HTML headers and offering a pre-built Sentry-instrumented request handler, improving distributed tracing capabilities across page loads.

Other Changes

v9.13.0

Compare Source

Important Changes

  • feat(node): Add support for winston logger (#​15983)

    Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like @sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.

    const winston = require('winston');
const Transport = require('winston-transport');

const transport = Sentry.createSentryWinstonTransport(Transport);

const logger = winston.createLogger({
  transports: [transport],
});

  • feat(core): Add wrapMcpServerWithSentry to instrument MCP servers from @modelcontextprotocol/sdk (#​16032)

    The Sentry SDK now supports instrumenting MCP servers from the @modelcontextprotocol/sdk package. Compatible with versions ^1.9.0 of the @modelcontextprotocol/sdk package.

    import { McpServer } from '@​modelcontextprotocol/sdk/server/mcp.js';

// Create an MCP server
const server = new McpServer({
  name: 'Demo',
  version: '1.0.0',
});

// Use the instrumented server in your application
const instrumentedServer = Sentry.wrapMcpServerWithSentry(server);

  • feat(core): Move console integration into core and add to cloudflare/vercel-edge (#​16024)

    Console instrumentation has been added to @sentry/cloudflare and @sentry/nextjs Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.

  • feat(bun): Support new Bun.serve APIs (#​16035)

    Bun 1.2.6 and above have a new Bun.serve API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.

    Thanks to @​Jarred-Sumner for helping us get this supported!

Other Changes
  • feat(browser): Warn on duplicate browserTracingIntegration (#​16042)
  • feat(core): Allow delayed sending with offline transport (#​15937)
  • feat(deps): Bump @​sentry/webpack-plugin from 3.2.4 to 3.3.1 (#​16057)
  • feat(vue): Apply stateTransformer to attachments in Pinia Plugin (#​16034)
  • fix(core): Run beforeSendLog after we process log (#​16019)
  • fix(nextjs): Don't show turbopack warning for newer Next.js canaries (#​16065)
  • fix(nextjs): Include patch version 0 for min supported 15.3.0 (#​16026)
  • fix(node): Ensure late init works with all integrations (#​16016)
  • fix(react-router): Pass unstable_sentryVitePluginOptions to cli instance (#​16033)
  • fix(serverless-aws): Overwrite root span name with GraphQL if set (#​16010)

v9.12.0

Compare Source

Important Changes

  • feat(feedback): Implement highlighting and hiding controls for screenshots (#​15951)

    The Sentry SDK now supports highlighting and hiding controls for screenshots in user feedback reports. This functionality is enabled by default.

  • feat(node): Add ignoreIncomingRequestBody callback to httpIntegration (#​15959)

    The httpIntegration now supports an optional ignoreIncomingRequestBody callback that can be used to skip capturing the body of incoming requests.

    Sentry.init({
  integrations: [
    Sentry.httpIntegration({
      ignoreIncomingRequestBody: (url, request) => {
        return request.method === 'GET' && url.includes('/api/large-payload');
      },
    }),
  ],
});

    The ignoreIncomingRequestBody callback receives the URL of the request and should return true if the body should be ignored.

  • Logging Improvements

    Sentry is adding support for structured logging. In this release we've made a variety of improvements to logging functionality in the Sentry SDKs.

    • feat(node): Add server.address to nodejs logs (#​16006)
    • feat(core): Add sdk name and version to logs (#​16005)
    • feat(core): Add sentry origin attribute to console logs integration (#​15998)
    • fix(core): Do not abbreviate message parameter attribute (#​15987)
    • fix(core): Prefix release and environment correctly (#​15999)
    • fix(node): Make log flushing logic more robust (#​15991)
Other Changes
  • build(aws-serverless): Include debug logs in lambda layer SDK bundle (#​15974)
  • feat(astro): Add tracking of errors during HTML streaming (#​15995)
  • feat(browser): Add onRequestSpanStart hook to browser tracing integration (#​15979)
  • feat(deps): Bump @​sentry/cli from 2.42.3 to 2.43.0 (#​16001)
  • feat(nextjs): Add captureRouterTransitionStart hook for capturing navigations (#​15981)
  • feat(nextjs): Mark clientside prefetch request spans with http.request.prefetch: true attribute (#​15980)
  • feat(nextjs): Un experimentify clientInstrumentationHook (#​15992)
  • feat(nextjs): Warn when client was initialized more than once (#​15971)
  • feat(node): Add support for SENTRY_DEBUG env variable (#​15972)
  • fix(tss-react): Change authToken type to string (#​15985)

Work in this release was contributed by @​Page- and @​Fryuni. Thank you for your contributions!

v9.11.0

Compare Source

  • feat(browser): Add http.redirect_count attribute to browser.redirect span (#​15943)
  • feat(core): Add consoleLoggingIntegration for logs (#​15955)
  • feat(core): Don't truncate error messages (#​15818)
  • feat(core): Emit debug log when transport execution fails (#​16009)
  • feat(nextjs): Add release injection in Turbopack (#​15958)
  • feat(nextjs): Record turbopack as tag (#​15928)
  • feat(nuxt): Base decision on source maps upload only on Nuxt source map settings (#​15859)
  • feat(react-router): Add sentryHandleRequest (#​15787)
  • fix(node): Use module instead of require for CJS check (#​15927)
  • fix(remix): Remove mentions of deprecated ErrorBoundary wrapper (#​15930)
  • ref(browser): Temporarily add sentry.previous_trace span attribute (#​15957)
  • ref(browser/core): Move all log flushing logic into clients (#​15831)
  • ref(core): Improve URL parsing utilities (#​15882)

v9.10.1

Compare Source

v9.10.0

Compare Source

Important Changes

  • feat: Add support for logs

    • feat(node): Add logging public APIs to Node SDKs (#​15764)
    • feat(core): Add support for beforeSendLog (#​15814)
    • feat(core): Add support for parameterizing logs (#​15812)
    • fix: Remove critical log severity level (#​15824)

    All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

    Logging is gated by an experimental option, _experiments.enableLogs.

    Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});

const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;

trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });

// Structured logging via the `fmt` helper function. When you use `fmt`, the string template and parameters are sent separately so they can be queried independently in Sentry.

info(fmt(`Updated profile for user ${userId}`));
warn(fmt(`Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}`));

    With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.

    const { info, warn } = Sentry.logger;

info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });

    To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.

  • feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#​15821)

    The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.

    const result = await Sentry.diagnoseSdkConnectivity();

    The result will be an object with the following properties:

    • "no-client-active": There was no active client when the function was called. This possibly means that the SDK was not initialized yet.
    • "sentry-unreachable": The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.
    • undefined: The SDK is working as expected.

  • SDK Tracing Performance Improvements for Node SDKs

    • feat: Stop using dropUndefinedKeys (#​15796)
    • feat(node): Only add span listeners for instrumentation when used (#​15802)
    • ref: Avoid dropUndefinedKeys for spanToJSON calls (#​15792)
    • ref: Avoid using SentryError for PromiseBuffer control flow (#​15822)
    • ref: Stop using dropUndefinedKeys in SpanExporter (#​15794)
    • ref(core): Avoid using SentryError for event processing control flow (#​15823)
    • ref(node): Avoid dropUndefinedKeys in Node SDK init (#​15797)
    • ref(opentelemetry): Avoid sampling work for non-root spans (#​15820)

    We've been hard at work making performance improvements to the Sentry Node SDKs (@sentry/node, @sentry/aws-serverless, @sentry/nestjs, etc.). We've seen that upgrading from 9.7.0 to 9.10.0 leads to 30-40% improvement in request latency for HTTP web-server applications that use tracing with high sample rates. Non web-server applications and non-tracing applications will see smaller improvements.

Other Changes
  • chore(deps): Bump rrweb to 2.35.0 (#​15825)
  • deps: Bump bundler plugins to 3.2.3 (#​15829)
  • feat: Always truncate stored breadcrumb messages to 2kb (#​15819)
  • feat(nextjs): Disable server webpack-handling for static builds (#​15751)
  • fix(nuxt): Don't override Nuxt options if undefined (#​15795)

v9.9.0

Compare Source

Important Changes

  • feat(nextjs): Support instrumentation-client.ts (#​15705)

    Next.js recently added a feature to support client-side (browser) instrumentation via a instrumentation-client.ts file.

    To be forwards compatible, the Sentry Next.js SDK will now pick up instrumentation-client.ts files even on older Next.js versions and add them to your client bundles. It is suggested that you either rename your sentry.client.config.ts file to instrumentation-client.ts, or if you already happen to have a instrumentation-client.ts file move the contents of sentry.client.config.ts to instrumentation-client.ts.

  • feat(browser): Add previous_trace span links (#​15569)

    The @sentry/browser SDK and SDKs based on @sentry/browser now emits a link from the first root span of a newly started trace to the root span of a previously started trace. You can control this feature via an option in browserTracingIntegration():

    Sentry.init({
  dsn: 'your-dsn-here'
  integrations: [
    Sentry.browserTracingIntegration({
      // Available settings:
      // - 'in-memory' (default): Stores previous trace information in memory
      // - 'session-storage': Stores previous trace information in the browser's `sessionStorage`
      // - 'off': Disable storing and sending previous trace information
      linkPreviousTrace: 'in-memory',
    }),
  ],
});

  • feat(browser): Add logger.X methods to browser SDK (#​15763)

    For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated methods.

    Sentry.init({
  dsn: 'your-dsn-here',
  _experiments: {
    enableLogs: true, // This is required to use the logging features
  },
});

Sentry.logger.info('This is a trace message', { userId: 123 });
// See MR for better documentation

    Please note that the logs product is still in early access. See the link above for more information.

Other Changes
  • feat(browser): Attach host as part of error message to "Failed to fetch" errors (#​15729)
  • feat(core): Add parseStringToURL method (#​15768)
  • feat(core): Optimize dropUndefinedKeys (#​15760)
  • feat(node): Add fastify shouldHandleError (#​15771)
  • fix(nuxt): Delete no longer needed Nitro 'close' hook (#​15790)
  • perf(nestjs): Remove usage of addNonEnumerableProperty (#​15766)
  • ref: Avoid some usage of dropUndefinedKeys() (#​15757)
  • ref: Remove some usages of dropUndefinedKeys() (#​15781)
  • ref(nextjs): Fix Next.js vercel-edge runtime package information (#​15789)

v9.8.0

Compare Source

  • feat(node): Implement new continuous profiling API spec (#​15635)
  • feat(profiling): Add platform to chunk envelope (#​15758)
  • feat(react): Export captureReactException method (#​15746)
  • fix(node): Check for res.end before passing to Proxy (#​15776)
  • perf(core): Add short-circuits to eventFilters integration (#​15752)
  • perf(node): Short circuit flushing on Vercel only for Vercel (#​15734)

v9.7.0

Compare Source

  • feat(core): Add captureLog method (#​15717)
  • feat(remix/cloudflare): Export sentryHandleError (#​15726)
  • fix(node): Always flush on Vercel before Lambda freeze (#​15602)
  • fix(node): Ensure incoming traces are propagated without HttpInstrumentation (#​15732)
  • fix(node): Use fatal level for unhandled rejections in strict mode (#​15720)
  • fix(nuxt): Delete Nuxt server template injection (#​15749)

v9.6.1

Compare Source

v9.6.0

Compare Source

Important Changes

  • feat(tanstackstart): Add @sentry/tanstackstart-react package and make @sentry/tanstackstart package a utility package (#​15629)

    Since TanStack Start is supposed to be a generic framework that supports libraries like React and Solid, the @sentry/tanstackstart SDK package was renamed to @sentry/tanstackstart-react to reflect that the SDK is specifically intended to be used for React TanStack Start applications. Note that the TanStack Start SDK is still in alpha status and may be subject to breaking changes in non-major package updates.

Other Changes
  • feat(astro): Accept all vite-plugin options (#​15638)
  • feat(deps): bump @​sentry/webpack-plugin from 3.2.1 to 3.2.2 (#​15627)
  • feat(tanstackstart): Refine initial API (#​15574)
  • fix(core): Ensure fill only patches functions (#​15632)
  • fix(nextjs): Consider pageExtensions when looking for instrumentation file (#​15701)
  • fix(remix): Null-check options (#​15610)
  • fix(sveltekit): Correctly parse angle bracket type assertions for auto instrumentation (#​15578)
  • fix(sveltekit): Guard process variable (#​15605)

Work in this release was contributed by @​angelikatyborska and @​nwalters512. Thank you for your contributions!

v9.5.0

Compare Source

Important Changes

We found some issues with the new feedback screenshot annotation where screenshots are not being generated properly. Due to this issue, we are reverting the feature.

  • Revert "feat(feedback) Allowing annotation via highlighting & masking (#​15484)" (#​15609)
Other Changes
  • Add cloudflare adapter detection and path generation (#​15603)
  • deps(nextjs): Bump rollup to 4.34.9 (#​15589)
  • feat(bun): Automatically add performance integrations (#​15586)
  • feat(replay): Bump rrweb to 2.34.0 (#​15580)
  • fix(browser): Call original function on early return from patched history API (#​15576)
  • fix(nestjs): Copy metadata in custom decorators (#​15598)
  • fix(react-router): Fix config type import (#​15583)
  • fix(remix): Use correct types export for @sentry/remix/cloudflare (#​15599)
  • fix(vue): Attach Pinia state only once per event (#​15588)

Work in this release was contributed by @​msurdi-a8c, @​namoscato, and @​rileyg98. Thank you for your contributions!

v9.4.0

Compare Source

  • feat(core): Add types for logs protocol and envelope (#​15530)
  • feat(deps): Bump @sentry/cli from 2.41.1 to 2.42.2 (#​15510)
  • feat(deps): Bump @sentry/webpack-plugin from 3.1.2 to 3.2.1 (#​15512)
  • feat(feedback) Allowing annotation via highlighting & masking (#​15484)
  • feat(nextjs): Add use client directive to client SDK entrypoints (#​15575)
  • feat(nextjs): Allow silencing of instrumentation warning (#​15555)
  • feat(sveltekit): Ensure AsyncLocalStorage async context strategy is used in Cloudflare Pages (#​15557)
  • fix(cloudflare): Make @cloudflare/workers-types an optional peer dependency (#​15554)
  • fix(core): Don't reverse values in event filters (#​15584)
  • fix(core): Handle normalization of null prototypes correctly (#​15556)
  • fix(nextjs): Only warn on missing onRequestError in version 15 (#​15553)
  • fix(node): Allow for undefined transport to be passed in (#​15560)
  • fix(wasm): Fix wasm integration stacktrace parsing for filename (#​15572)
  • perf(node): Store normalized request for processing (#​15570)

v9.3.0

Compare Source

Important Changes

With this release we're publishing two new SDKs in experimental alpha stage:

  • feat(tanstackstart): Add TanStack Start SDK (#​15523)

For details please refer to the README

  • feat(react-router): Add React Router SDK (#​15524)

For details please refer to the README

  • feat(remix): Add support for Hydrogen (#​15450)

This MR adds support for Shopify Hydrogen applications running on MiniOxygen runtime.

Other Changes
  • feat(core): Add forceTransaction to trpc middleware options (#​15519)
  • feat(core): Default filter unactionable error (#​15527)
  • feat(core): Rename inboundFiltersIntegration to eventFiltersIntegration (#​15434)
  • feat(deps): bump @​prisma/instrumentation from 6.2.1 to 6.4.1 (#​15480)
  • feat(react-router): Add build-time config (#​15406)
  • feat(replay): Bump rrweb to 2.33.0 (#​15514)
  • fix(core): Fix allowUrls and denyUrls for linked and aggregate exceptions (#​15521)
  • fix(nextjs): Don't capture devmode server-action redirect errors (#​15485)
  • fix(nextjs): warn about missing onRequestError handler #​15488)
  • fix(nextjs): Prevent wrong culprit from showing up for clientside error events #​15475)
  • fix(nuxt): Ignore 300-400 status codes on app errors in Nuxt (#​15473)
  • fix(react): Add support for cross-usage of React Router instrumentations (#​15283)
  • fix(sveltekit): Guard process check when flushing events (#​15516)

Work in this release was contributed by @​GerryWilko and @​leoambio. Thank you for your contributions!

v9.2.0

Compare Source

Important Changes

This release adds full tracing support for Express v5, and improves tracing support for Nest.js 11 (which uses Express v5) in the Nest.js SDK.

  • feat(sveltekit): Add Support for Cloudflare (#​14672)

This release adds support for deploying SvelteKit applications to Cloudflare Pages. A docs update with updated instructions will follow shortly. Until then, you can give this a try by setting up the SvelteKit SDK as usual and then following the instructions outlined in the MR.

Thank you @​SG60 for contributing this feature!

Other Changes
  • feat(core): Add addLink(s) to Sentry span (#​15452)
  • feat(core): Add links to span options (#​15453)
  • feat(deps): Bump @​sentry/webpack-plugin from 2.22.7 to 3.1.2 (#​15328)
  • feat(feedback): Disable Feedback submit & cancel buttons while submitting (#​15408)
  • feat(nextjs): Add experimental flag to not strip origin information from different origin stack frames (#​15418)
  • feat(nuxt): Add enableNitroErrorHandler to server options (#​15444)
  • feat(opentelemetry): Add addLink(s) to span (#​15387)
  • feat(opentelemetry): Add links to span options (#​15403)
  • feat(replay): Expose rrweb recordCrossOriginIframes under _experiments (#​14916)
  • fix(browser): Ensure that performance.measure spans have a positive duration (#​15415)
  • fix(bun): Includes correct sdk metadata (#​15459)
  • fix(core): Add Google gmo error to Inbound Filters (#​15432)
  • fix(core): Ensure http.client span descriptions don't contain query params or fragments (#​15404)
  • fix(core): Filter out unactionable Facebook Mobile browser error (#​15430)
  • fix(nestjs): Pin dependency on @opentelemetry/instrumentation (#​15419)
  • fix(nuxt): Only use filename with file extension from command (#​15445)
  • fix(nuxt): Use SentryNuxtServerOptions type for server init (#​15441)
  • fix(sveltekit): Avoid loading vite config to determine source maps setting (#​15440)
  • ref(profiling-node): Bump chunk interval to 60s (#​15361)

Work in this release was contributed by @​6farer, @​dgavranic and @​SG60. Thank you for your contributions!

v9.1.0

Compare Source

Work in this release was contributed by @​Zen-cronic and @​filips-alpe. Thank you for your contribution!

v9.0.1

Compare Source

  • ref(flags): rename unleash integration param (#​15343)

v9.0.0

Compare Source

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.

How To Upgrade

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

Breaking Changes
  • doc(deno)!: Make Deno v2 the minimum supported version (#​15085)
  • feat!: Bump typescript to ~5.0.0 (#​14758)
  • feat!: Drop nitro-utils package (#​14998)
  • feat!: Only collect ip addresses with sendDefaultPii: true (#​15084)
  • feat!: Remove autoSessionTracking option (#​14802)
  • feat!: Remove enableTracing (#​15078)
  • feat!: Remove getCurrentHub(), Hub, and getCurrentHubShim() (#​15122)
  • feat!: Remove spanId from propagation context (#​14733)
  • feat!: Remove deprecated and unused code (#​15077)
  • feat!: Remove metrics API from the JS SDK (#​14745)
  • feat!: Require Node >=18 as minimum supported version (#​14749)
  • feat(astro)!: Respect user-specified source map setting (#​14941)
  • feat(browser)!: Remove captureUserFeedback method (#​14820)
  • feat(build)!: Drop pre-ES2020 polyfills (#​14882)
  • feat(core)!: Add normalizedRequest to samplingContext (#​14902)
  • feat(core)!: Always use session from isolation scope (#​14860)
  • feat(core)!: Pass root spans to beforeSendSpan and disallow returning null (#​14831)
  • feat(core)!: Remove BAGGAGE_HEADER_NAME export (#​14785)
  • feat(core)!: Remove TransactionNamingScheme type (#​14865)
  • feat(core)!: Remove addOpenTelemetryInstrumentation method (#​14792)
  • feat(core)!: Remove arrayify method (#​14782)
  • feat(core)!: Remove debugIntegration and sessionTimingIntegration (#​14747)
  • feat(core)!: Remove flatten method (#​14784)
  • feat(core)!: Remove getDomElement method (#​14797)
  • feat(core)!: Remove makeFifoCache method (#​14786)
  • feat(core)!: Remove memoBuilder export & WeakSet fallback (#​14859)
  • feat(core)!: Remove transactionContext from samplingContext (#​14904)
  • feat(core)!: Remove urlEncode method (#​14783)
  • feat(core)!: Remove deprecated Request type (#​14858)
  • feat(core)!: Remove deprecated request data methods (#​14896)
  • feat(core)!: Remove standalone Client interface & deprecate BaseClient (#​14800)
  • feat(core)!: Remove validSeverityLevels export (#​14765)
  • feat(core)!: Stop accepting event as argument for recordDroppedEvent (#​14999)
  • feat(core)!: Stop setting user in requestDataIntegration (#​14898)
  • feat(core)!: Type sdkProcessingMetadata more strictly (#​14855)
  • feat(core)!: Update hasTracingEnabled to consider empty trace config (#​14857)
  • feat(core)!: Update requestDataIntegration handling (#​14806)
  • feat(deno)!: Remove deno prepack (#​14829)
  • feat(ember)!: Officially drop support for ember <=3.x (#​15032)
  • feat(nestjs)!: Move nestIntegration into nest sdk and remove setupNestErrorHandler (#​14751)
  • feat(nestjs)!: Remove @WithSentry decorator (#​14762)
  • feat(nestjs)!: Remove SentryService (#​14759)
  • feat(nextjs)!: Don't rely on Next.js Build ID for release names (#​14939)
  • feat(nextjs)!: Remove experimental_captureRequestError (#​14607)
  • feat(nextjs)!: Respect user-provided source map generation settings (#​14956)
  • feat(node)!: Add support for Prisma v6 and drop v5 support (#​15120)
  • feat(node)!: Avoid http spans by default for custom OTEL setups (#​14678)
  • feat(node)!: Collect request sessions via HTTP instrumentation (#​14658)
  • feat(node)!: Remove processThreadBreadcrumbIntegration (#​14666)
  • feat(node)!: Remove fine grained registerEsmLoaderHooks (#​15002)
  • feat(opentelemetry)!: Exclusively pass root spans through sampling pipeline (#​14951)
  • feat(pinia)!: Include state of all stores in breadcrumb (#​15312)
  • feat(react)!: Raise minimum supported TanStack Router version to 1.63.0 (#​15030)
  • feat(react)!: Remove deprecated getNumberOfUrlSegments method (#​14744)
  • feat(react)!: Remove deprecated react router methods (#​14743)
  • feat(react)!: Update ErrorBoundary componentStack type (#​14742)
  • feat(remix)!: Drop support for Remix v1 (#​14988)
  • feat(remix)!: Remove autoInstrumentRemix option (#​15074)
  • feat(solidstart)!: Default to --import setup and add autoInjectServerSentry (#​14862)
  • feat(solidstart)!: No longer export sentrySolidStartVite (#​15143)
  • feat(solidstart)!: Respect user-provided source map setting (#​14979)
  • feat(svelte)!: Disable component update tracking by default (#​15265)
  • feat(sveltekit)!: Drop support for SvelteKit @​1.x (#​15037)
  • feat(sveltekit)!: Remove fetchProxyScriptNonce option (#​15123)
  • feat(sveltekit)!: Respect user-provided source map generation settings (#​14886)
  • feat(utils)!: Remove @sentry/utils package (#​14830)
  • feat(vue)!: Remove configuring Vue tracing options anywhere else other than through the vueIntegration's tracingOptions option (#​14856)
  • feat(vue/nuxt)!: No longer create "update" spans for component tracking by default (#​14602)
  • fix(node)!: Fix name of vercelAIIntegration to VercelAI (#​15298)
  • fix(vue)!: Remove logError from vueIntegration (#​14958)
  • ref!: Don't polyfill optional chaining and nullish coalescing (#​14603)
  • ref(core)!: Cleanup internal types, including ReportDialogOptions (#​14861)
  • ref(core)!: Mark exceptions from captureConsoleIntegration as handled: true by default (#​14734)
  • ref(core)!: Move shutdownTimeout option type from core to node (#​15217)
  • ref(core)!: Remove Scope type interface in favor of using Scope class (#​14721)
  • ref(core)!: Remove backwards compatible SentryCarrier type (#​14697)
Other Changes

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!

v8.55.0

Compare Source

Important Changes
  • chore(ci/v8): Switch lambda layer name to SentryNodeServerlessSDKv8 (#​15351)

The SentryNodeServerlessSDK AWS Lambda Layer will stop receiving updates. If you intend to stay on v8 and receive updates use SentryNodeServerlessSDKv8 instead.

Other Changes
  • feat(flags/v8): add Statsig browser integration (#​15347)
  • feat(v8/node): Add missing vercelAIIntegration export (#​15339)
  • feat(v8/nuxt): Add enabled to disable Sentry module (#​15337) (#​15381)
  • feat(v8/vue): Support Pinia v3 (#​15384)
  • fix(astro): Add vue to registerEsmLoaderHooks (#​15352)
  • fix(react/v8): Support lazy-loaded routes and components (#​15281)
  • fix(v8/nuxt): Detect Azure Function runtime for flushing with timeout (#​15297)
  • fix(v8/solidstart): Do not copy release-injection map file (#​15304)
  • fix(v8/svelte): Guard component tracking beforeUpdate call (#​15262)

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

Bundle size 📦

Path Size
@​sentry/browser 23.3 KB
@​sentry/browser - with treeshaking flags 23.17 KB
@​sentry/browser (incl. Tracing) 35.9 KB
@​sentry/browser (incl. Tracing, Replay) 73.27 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 66.71 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 77.57 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 89.5 KB
@​sentry/browser (incl. Feedback) 39.51 KB
@​sentry/browser (incl. sendFeedback) 27.91 KB
@​sentry/browser (incl. FeedbackAsync) 32.71 KB
@​sentry/react 25.98 KB
@​sentry/react (incl. Tracing) 38.71 KB
@​sentry/vue 27.58 KB
@​sentry/vue (incl. Tracing) 37.75 KB
@​sentry/svelte 23.46 KB
CDN Bundle 24.49 KB
CDN Bundle (incl. Tracing) 37.6 KB
CDN Bundle (incl. Tracing, Replay) 72.9 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 78.23 KB
CDN Bundle - uncompressed 71.92 KB
CDN Bundle (incl. Tracing) - uncompressed 111.52 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 225.78 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 238.88 KB
@​sentry/nextjs (client) 38.96 KB
@​sentry/sveltekit (client) 36.4 KB
@​sentry/node 162.85 KB
@​sentry/node - without tracing 99.14 KB
@​sentry/aws-serverless 131.23 KB

v8.54.0

Compare Source

  • feat(v8/deps): Upgrade all OpenTelemetry dependencies (#​15098)
  • fix(node/v8): Add compatibility layer for Prisma v5 (#​15210)

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

v8.53.0

Compare Source

  • feat(v8/nuxt): Add url to SourcemapsUploadOptions (#​15202)
  • fix(v8/react): fromLocation can be undefined in Tanstack Router Instrumentation (#​15237)

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

v8.52.1

Compare Source

  • fix(v8/nextjs): Fix nextjs build warning (#​15226)
  • ref(v8/browser): Add protocol attributes to resource spans #​15224
  • ref(v8/core): Don't set this.name to new.target.prototype.constructor.name (#​15222)

Work in this release was contributed by @​Zen-cronic. Thank you for your contribution!

v8.52.0

Compare Source

Important Changes
  • feat(solidstart): Add 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 '@&#8203;solidjs/start/config';
import { withSentry } from '@&#8203;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:

  1. (recommended) Provide an --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
  2. Add 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',
  },
);
Other Changes
  • feat(v8/core): Add client outcomes for breadcrumbs buffer (#​15149)
  • feat(v8/core): Improve error formatting in ZodErrors integration (#​15155)
  • fix(v8/bun): Ensure instrumentation of Bun.serve survives a server reload (#​15157)
  • fix(v8/core): Pass module into loadModule (#​15139) (#​15166)

Work in this release was contributed by @​jahands, @​jrandolf, and @​nathankleyn. Thank you for your contributions!

v8.51.0

Compare Source

Important Changes

  • 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:

    1. Install the @prisma/instrumentation package on version 6.

    2. Pass a new PrismaInstrumentation() instance as exported from @prisma/instrumentation to the prismaInstrumentation option:

      import { PrismaInstrumentation } from '@&#8203;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.

    3. Remove the previewFeatures = ["tracing"] option from the client generator block of your Prisma schema.

Other Changes
  • feat(v8/browser): Add multiplexedtransport.js CDN bundle (#​15046)
  • feat(v8/browser): Add Unleash integration (#​14948)
  • feat(v8/deno): Deprecate Deno SDK as published on deno.land (#​15121)
  • feat(v8/sveltekit): Deprecate fetchProxyScriptNonce option (#​15011)
  • fix(v8/aws-lambda): Avoid overwriting root span name (#​15054)
  • fix(v8/core): fatal events should set session as crashed (#​15073)
  • fix(v8/node/nestjs): Use method on current fastify request (#​15104)

Work in this release was contributed by @​tjhiggins, and @​nwalters512. Thank you for your contributions!

v8.50.0

Compare Source

  • feat(v8/react): Add support for React Router createMemoryRouter (#​14985)

v8.49.0

Compare Source

  • feat(v8/browser): Flush offline queue on flush and browser online event (#​14969)
  • feat(v8/react): Add a handled prop to ErrorBoundary (#​14978)
  • fix(profiling/v8): Don't put require, __filename and __dirname on global object (#​14952)
  • fix(v8/node): Enforce that ContextLines integration does not leave open file handles (#​14997)
  • fix(v8/replay): Disable mousemove sampling in rrweb for iOS browsers (#​14944)
  • fix(v8/sveltekit): Ensure source maps deletion is called after source ma… (#​14963)
  • fix(v8/vue): Re-throw error when no errorHandler exists (#​14943)

Work in this release was contributed by @​HHK1 and @​mstrokin. Thank you for your contributions!

v8.48.0

Compare Source

Deprecations

  • feat(v8/core): Deprecate getDomElement method (#​14799)

    Deprecates getDomElement. There is no replacement.

Other changes
  • fix(nestjs/v8): Use correct main/module path in package.json (#​14791)
  • fix(v8/core): Use consistent continueTrace implementation in core (#​14819)
  • fix(v8/node): Correctly resolve debug IDs for ANR events with custom appRoot (#​14823)
  • fix(v8/node): Ensure NODE_OPTIONS is not passed to worker threads (#​14825)
  • fix(v8/angular): Fall back to element tagName when name is not provided to TraceDirective (#​14828)
  • fix(aws-lambda): Remove version suffix from lambda layer (#​14843)
  • fix(v8/node): Ensure express requests are properly handled (#​14851)
  • feat(v8/node): Add openTelemetrySpanProcessors option (#​14853)
  • fix(v8/react): Use Set as the allRoutes container. (#​14878) (#​14884)
  • fix(v8/react): Improve handling of routes nested under path="/" (#​14897)
  • feat(v8/core): Add normalizedRequest to samplingContext (#​14903)
  • fix(v8/feedback): Avoid lazy loading code for syncFeedbackIntegration (#​14918)

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

v8.47.0

Compare Source

  • feat(v8/core): Add updateSpanName helper function (#​14736)
  • feat(v8/node): Do not overwrite prisma db.system in newer Prisma versions (#​14772)
  • feat(v8/node/deps): Bump @​prisma/instrumentation from 5.19.1 to 5.22.0 (#​14755)
  • feat(v8/replay): Mask srcdoc iframe contents per default (#​14779)
  • ref(v8/nextjs): Fix typo in source maps deletion warning (#​14776)

Work in this release was contributed by @​aloisklink and @​benjick. Thank you for your contributions!

v8.46.0

Compare Source

  • feat: Allow capture of more than 1 ANR event [v8] (#​14713)
  • feat(node): Detect Railway release name [v8] (#​14714)
  • fix: Normalise ANR debug image file paths if appRoot was supplied [v8] (#​14709)
  • fix(nuxt): Remove build config from tsconfig (#​14737)

Work in this release was contributed by @​conor-ob. Thank you for your contribution!

v8.45.1

Compare Source

  • fix(feedback): Return when the sendFeedback promise resolves (#​14683)

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

v8.45.0

Compare Source

  • feat(core): Add handled option to captureConsoleIntegration (#​14664)
  • feat(browser): Attach virtual stack traces to HttpClient events (#​14515)
  • feat(replay): Upgrade rrweb packages to 2.31.0 (#​14689)
  • fix(aws-serverless): Remove v8 layer as it overwrites the current layer for docs (#​14679)
  • fix(browser): Mark stack trace from captureMessage with attachStacktrace: true as synthetic (#​14668)
  • fix(core): Mark stack trace from captureMessage with attatchStackTrace: true as synthetic (#​14670)
  • fix(core): Set level in server runtime captureException (#​10587)
  • fix(profiling-node): Guard invocation of native profiling methods (#​14676)
  • fix(nuxt): Inline nitro-utils function (#​14680)
  • fix(profiling-node): Ensure profileId is added to transaction event (#​14681)
  • fix(react): Add React Router Descendant Routes support (#​14304)
  • fix: Disable ANR and Local Variables if debugger is enabled via CLI args (#​14643)

Work in this release was contributed by @​anonrig and @​Zih0. Thank you for your contributions!

v8.44.0

Compare Source

Deprecations

  • feat: Deprecate autoSessionTracking (#​14640)

    Deprecates autoSessionTracking. To enable session tracking, it is recommended to unset autoSessionTracking and ensure that either, in browser environments the browserSessionIntegration is added, or in server environments the httpIntegration is added.

    To disable session tracking, it is recommended to unset autoSessionTracking and to remove the browserSessionIntegration in browser environments, or in server environments configure the httpIntegration with the trackIncomingRequestsAsSessions option set to false.

Other Changes
  • feat: Reword log message around unsent spans (#​14641)
  • feat(opentelemetry): Set response context for http.server spans (#​14634)
  • fix(google-cloud-serverless): Update homepage link in package.json (#​14411)
  • fix(nuxt): Add unbuild config to not fail on warn (#​14662)

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

v8.43.0

Compare Source

Important Changes

  • feat(nuxt): Add option autoInjectServerSentry (no default import()) (#​14553)

    Using the dynamic import() as the default behavior for initializing the SDK on the server-side did not work for every project. The default behavior of the SDK has been changed, and you now need to use the --import flag to initialize Sentry on the server-side to leverage full functionality.

    Example with --import:

    node --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs

    In case you are not able to use the --import flag, you can enable auto-injecting Sentry in the nuxt.config.ts (comes with limitations):

    sentry: {
  autoInjectServerSentry: 'top-level-import', // or 'experimental_dynamic-import'
},

  • feat(browser): Adds LaunchDarkly and OpenFeature integrations (#​14207)

    Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:

    import * as Sentry from '@&#8203;sentry/browser';

Sentry.init({
  integrations: [
    // Track LaunchDarkly feature flags
    Sentry.launchDarklyIntegration(),
    // Track OpenFeature feature flags
    Sentry.openFeatureIntegration(),
  ],
});

  • feat(browser): Add featureFlagsIntegration for custom tracking of flag evaluations (#​14582)

    Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:

    import * as Sentry from '@&#8203;sentry/browser';

const featureFlagsIntegrationInstance = Sentry.featureFlagsIntegration();

Sentry.init({
  // Initialize the SDK with the feature flag integration
  integrations: [featureFlagsIntegrationInstance],
});

// Manually track a feature flag
featureFlagsIntegrationInstance.addFeatureFlag('my-feature', true);

  • feat(astro): Add Astro 5 support (#​14613)

    With this release, the Sentry Astro SDK officially supports Astro 5.

Deprecations

  • feat(nextjs): Deprecate typedef for hideSourceMaps (#​14594)

    The functionality of hideSourceMaps was removed in version 8 but was forgotten to be deprecated and removed. It will be completely removed in the next major version.

  • feat(core): Deprecate APIs around RequestSessions (#​14566)

    The APIs around RequestSessions are mostly used internally. Going forward the SDK will not expose concepts around RequestSessions. Instead, functionality around server-side Release Health will be managed in integrations.

Other Changes
  • feat(browser): Add browserSessionIntegration (#​14551)
  • feat(core): Add raw_security envelope types (#​14562)
  • feat(deps): Bump @​opentelemetry/instrumentation from 0.55.0 to 0.56.0 (#​14625)
  • feat(deps): Bump @​sentry/cli from 2.38.2 to 2.39.1 (#​14626)
  • feat(deps): Bump @​sentry/rollup-plugin from 2.22.6 to 2.22.7 (#​14622)
  • feat(deps): Bump @​sentry/webpack-plugin from 2.22.6 to 2.22.7 (#​14623)
  • feat(nestjs): Add fastify support (#​14549)
  • feat(node): Add @​vercel/ai instrumentation (#​13892)
  • feat(node): Add disableAnrDetectionForCallback function (#​14359)
  • feat(node): Add trackIncomingRequestsAsSessions option to http integration (#​14567)
  • feat(nuxt): Add option autoInjectServerSentry (no default import()) (#​14553)
  • feat(nuxt): Add warning when Netlify or Vercel build is discovered (#​13868)
  • feat(nuxt): Improve serverless event flushing and scope isolation (#​14605)
  • feat(opentelemetry): Stop looking at propagation context for span creation (#​14481)
  • feat(opentelemetry): Update OpenTelemetry dependencies to ^1.29.0 (#​14590)
  • feat(opentelemetry): Update OpenTelemetry dependencies to 1.28.0 (#​14547)
  • feat(replay): Upgrade rrweb packages to 2.30.0 (#​14597)
  • fix(core): Decode filename and module stack frame properties in Node stack parser (#​14544)
  • fix(core): Filter out unactionable CEFSharp promise rejection error by default (#​14595)
  • fix(nextjs): Don't show warning about devtool option (#​14552)
  • fix(nextjs): Only apply tracing metadata to data fetcher data when data is an object (#​14575)
  • fix(node): Guard against invalid maxSpanWaitDuration values (#​14632)
  • fix(react): Match routes with parseSearch option in TanStack Router instrumentation (#​14328)
  • fix(sveltekit): Fix git SHA not being picked up for release (#​14540)
  • fix(types): Fix generic exports with default (#​14576)

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

v8.42.0

Compare Source

Important Changes
Deprecations

  • feat: Warn about source-map generation (#​14533)

    In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.

    With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.

  • feat(nuxt): Deprecate tracingOptions in favor of vueIntegration (#​14530)

    Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:

    • In Sentry.init()
    • Inside tracingOptions in Sentry.init()

    For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration() and its tracingOptions option to configure tracing options in the Nuxt SDK:

    // sentry.client.config.ts
import * as Sentry from '@&#8203;sentry/nuxt';

Sentry.init({
  // ...
  integrations: [
    Sentry.vueIntegration({
      tracingOptions: {
        trackComponents: true,
      },
    }),
  ],
});
Other Changes
  • feat(browser-utils): Update web-vitals to v4.2.4 (#​14439)
  • feat(nuxt): Expose vueIntegration (#​14526)
  • fix(feedback): Handle css correctly in screenshot mode (#​14535)

v8.41.0

Compare Source

Important Changes

  • meta(nuxt): Require minimum Nuxt v3.7.0 (#​14473)

    We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above. Additionally, the SDK requires the implicit nitropack dependency to satisfy version ^2.10.0 and ofetch to satisfy ^1.4.0. It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.

Deprecations

We are deprecating a few APIs which will be removed in the next major.

The following deprecations will potentially affect you:

  • feat(core): Update & deprecate undefined option handling (#​14450)

    In the next major version we will change how passing undefined to tracesSampleRate / tracesSampler / enableTracing will behave.

    Currently, doing the following:

    Sentry.init({
  tracesSampleRate: undefined,
});

    Will result in tracing being enabled (although no spans will be generated) because the tracesSampleRate key is present in the options object. In the next major version, this behavior will be changed so that passing undefined (or rather having a tracesSampleRate key) will result in tracing being disabled, the same as not passing the option at all. If you are currently relying on undefined being passed, and and thus have tracing enabled, it is recommended to update your config to set e.g. tracesSampleRate: 0 instead, which will also enable tracing in v9.

    The same applies to tracesSampler and enableTracing.

  • feat(core): Log warnings when returning null in beforeSendSpan (#​14433)

    Currently, the beforeSendSpan option in Sentry.init() allows you to drop individual spans from a trace by returning null from the hook. Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.

    With the next major version the beforeSendSpan API can only be used to mutate spans, but no longer to drop them. With this release the SDK will warn you if you are using this API to drop spans. Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.

    Additionally, with the next major version, root spans will also be passed to beforeSendSpan.

  • feat(utils): Deprecate @sentry/utils (#​14431)

    With the next major version the @sentry/utils package will be merged into the @sentry/core package. It is therefore no longer recommended to use the @sentry/utils package.

  • feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the vueIntegration's tracingOptions option (#​14385)

    Currently it is possible to configure tracing options in various places in the Sentry Vue SDK:

    • In Sentry.init()
    • Inside tracingOptions in Sentry.init()
    • In the vueIntegration() options
    • Inside tracingOptions in the vueIntegration() options

    Because this is a bit messy and confusing to document, the only recommended way to configure tracing options going forward is through the tracingOptions in the vueIntegration(). The other means of configuration will be removed in the next major version of the SDK.

  • feat: Deprecate registerEsmLoaderHooks.include and registerEsmLoaderHooks.exclude (#​14486)

    Currently it is possible to define registerEsmLoaderHooks.include and registerEsmLoaderHooks.exclude options in Sentry.init() to only apply ESM loader hooks to a subset of modules. This API served as an escape hatch in case certain modules are incompatible with ESM loader hooks.

    Since this API was introduced, a way was found to only wrap modules that there exists instrumentation for (meaning a vetted list). To only wrap modules that have instrumentation, it is recommended to instead set registerEsmLoaderHooks.onlyIncludeInstrumentedModules to true.

    Note that onlyIncludeInstrumentedModules: true will become the default behavior in the next major version and the registerEsmLoaderHooks will no longer accept fine-grained options.

The following deprecations will most likely not affect you unless you are building an SDK yourself:

  • feat(core): Deprecate arrayify (#​14405)
  • feat(core): Deprecate flatten (#​14454)
  • feat(core): Deprecate urlEncode (#​14406)
  • feat(core): Deprecate validSeverityLevels (#​14407)
  • feat(core/utils): Deprecate getNumberOfUrlSegments (#​14458)
  • feat(utils): Deprecate memoBuilder, BAGGAGE_HEADER_NAME, and makeFifoCache (#​14434)
  • feat(utils/core): Deprecate addRequestDataToEvent and extractRequestData (#​14430)
Other Changes
  • feat: Streamline sentry-trace, baggage and DSC handling (#​14364)
  • feat(core): Further optimize debug ID parsing (#​14365)
  • feat(node): Add openTelemetryInstrumentations option (#​14484)
  • feat(nuxt): Add filter for not found source maps (devtools) (#​14437)
  • feat(nuxt): Only delete public source maps (#​14438)
  • fix(nextjs): Don't report NEXT_REDIRECT from browser (#​14440)
  • perf(opentelemetry): Bucket spans for cleanup (#​14154)

Work in this release was contributed by @​NEKOYASAN and @​fmorett. Thank you for your contributions!

v8.40.0

Compare Source

Important Changes

  • feat(angular): Support Angular 19 (#​14398)

    The @sentry/angular SDK can now be used with Angular 19. If you're upgrading to the new Angular version, you might want to migrate from the now deprecated APP_INITIALIZER token to provideAppInitializer. In this case, change the Sentry TraceService initialization in app.config.ts:

    // Angular 18
export const appConfig: ApplicationConfig = {
  providers: [
    // other providers
    {
      provide: TraceService,
      deps: [Router],
    },
    {
      provide: APP_INITIALIZER,
      useFactory: () => () => {},
      deps: [TraceService],
      multi: true,
    },
  ],
};

// Angular 19
export const appConfig: ApplicationConfig = {
  providers: [
    // other providers
    {
      provide: TraceService,
      deps: [Router],
    },
    provideAppInitializer(() => {
      inject(TraceService);
    }),
  ],
};

  • feat(core): Deprecate debugIntegration and sessionTimingIntegration (#​14363)

    The debugIntegration was deprecated and will be removed in the next major version of the SDK. To log outgoing events, use Hook Options (beforeSend, beforeSendTransaction, ...).

    The sessionTimingIntegration was deprecated and will be removed in the next major version of the SDK. To capture session durations alongside events, use Context (Sentry.setContext()).

  • feat(nestjs): Deprecate @WithSentry in favor of @SentryExceptionCaptured (#​14323)

    The @WithSentry decorator was deprecated. Use @SentryExceptionCaptured instead. This is a simple renaming and functionality stays identical.

  • feat(nestjs): Deprecate SentryTracingInterceptor, SentryService, SentryGlobalGenericFilter, SentryGlobalGraphQLFilter (#​14371)

    The SentryTracingInterceptor was deprecated. If you are using @sentry/nestjs you can safely remove any references to the SentryTracingInterceptor. If you are using another package migrate to @sentry/nestjs and remove the SentryTracingInterceptor afterwards.

    The SentryService was deprecated and its functionality was added to Sentry.init. If you are using @sentry/nestjs you can safely remove any references to the SentryService. If you are using another package migrate to @sentry/nestjs and remove the SentryService afterwards.

    The SentryGlobalGenericFilter was deprecated. Use the SentryGlobalFilter instead which is a drop-in replacement.

    The SentryGlobalGraphQLFilter was deprecated. Use the SentryGlobalFilter instead which is a drop-in replacement.

  • feat(node): Deprecate nestIntegration and setupNestErrorHandler in favor of using @sentry/nestjs (#​14374)

    The nestIntegration and setupNestErrorHandler functions from @sentry/node were deprecated and will be removed in the next major version of the SDK. If you're using @sentry/node in a NestJS application, we recommend switching to our new dedicated @sentry/nestjs package.

Other Changes
  • feat(browser): Send additional LCP timing info (#​14372)
  • feat(replay): Clear event buffer when full and in buffer mode (#​14078)
  • feat(core): Ensure normalizedRequest on sdkProcessingMetadata is merged (#​14315)
  • feat(core): Hoist everything from @sentry/utils into @sentry/core (#​14382)
  • fix(core): Do not throw when trying to fill readonly properties (#​14402)
  • fix(feedback): Fix __self and __source attributes on feedback nodes (#​14356)
  • fix(feedback): Fix non-wrapping form title (#​14355)
  • fix(nextjs): Update check for not found navigation error (#​14378)

v8.39.0

Compare Source

Important Changes
  • feat(nestjs): Instrument event handlers (#​14307)

The @sentry/nestjs SDK will now capture performance data for NestJS Events (@nestjs/event-emitter)

Other Changes
  • feat(nestjs): Add alias @SentryExceptionCaptured for @WithSentry (#​14322)
  • feat(nestjs): Duplicate SentryService behaviour into @sentry/nestjs SDK init() (#​14321)
  • feat(nestjs): Handle GraphQL contexts in SentryGlobalFilter (#​14320)
  • feat(node): Add alias childProcessIntegration for processThreadBreadcrumbIntegration and deprecate it (#​14334)
  • feat(node): Ensure request bodies are reliably captured for http requests (#​13746)
  • feat(replay): Upgrade rrweb packages to 2.29.0 (#​14160)
  • fix(cdn): Ensure _sentryModuleMetadata is not mangled (#​14344)
  • fix(core): Set sentry.source attribute to custom when calling span.updateName on SentrySpan (#​14251)
  • fix(mongo): rewrite Buffer as ? during serialization (#​14071)
  • fix(replay): Remove replay id from DSC on expired sessions (#​14342)
  • ref(profiling) Fix electron crash (#​14216)
  • ref(types): Deprecate Request type in favor of RequestEventData (#​14317)
  • ref(utils): Stop setting transaction in requestDataIntegration (#​14306)
  • ref(vue): Reduce bundle size for starting application render span (#​14275)

v8.38.0

Compare Source

  • docs: Improve docstrings for node otel integrations (#​14217)
  • feat(browser): Add moduleMetadataIntegration lazy loading support (#​13817)
  • feat(core): Add trpc path to context in trpcMiddleware (#​14218)
  • feat(deps): Bump @​opentelemetry/instrumentation-amqplib from 0.42.0 to 0.43.0 (#​14230)
  • feat(deps): Bump @​sentry/cli from 2.37.0 to 2.38.2 (#​14232)
  • feat(node): Add knex integration (#​13526)
  • feat(node): Add tedious integration (#​13486)
  • feat(utils): Single implementation to fetch debug ids (#​14199)
  • fix(browser): Avoid recording long animation frame spans starting before their parent span (#​14186)
  • fix(node): Include debug_meta with ANR events (#​14203)
  • fix(nuxt): Fix dynamic import rollup plugin to work with latest nitro (#​14243)
  • fix(react): Support wildcard routes on React Router 6 (#​14205)
  • fix(spotlight): Export spotlightBrowserIntegration from the main browser package (#​14208)
  • ref(browser): Ensure start time of interaction root and child span is aligned (#​14188)
  • ref(nextjs): Make build-time value injection turbopack compatible (#​14081)

Work in this release was contributed by @​grahamhency, @​Zen-cronic, @​gilisho and @​phuctm97. Thank you for your contributions!

v8.37.1

Compare Source

v8.37.0

Compare Source

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

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

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

v8.36.0

Compare Source

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

v8.35.0

Compare Source

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

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 '@&#8203;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!

v8.34.0

Compare Source

Important Changes

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.

Other Changes
  • feat(cdn): Export getReplay in replay CDN bundles (#​13881)
  • feat(replay): Clear fallback buffer when switching buffers (#​13914)
  • feat(replay): Upgrade rrweb packages to 2.28.0 (#​13732)
  • fix(docs): Correct supported browsers due to globalThis (#​13788)
  • fix(nextjs): Adjust path to requestAsyncStorageShim.js template file (#​13928)
  • fix(nextjs): Detect new locations for request async storage to support Next.js v15.0.0-canary.180 and higher (#​13920)
  • fix(nextjs): Drop _not-found spans for all HTTP methods (#​13906)
  • fix(nextjs): Fix resolution of request storage shim fallback (#​13929)
  • fix(node): Ensure graphql options are correct when preloading (#​13769)
  • fix(node): Local variables handle error (#​13827)
  • fix(node): Remove dataloader instrumentation from default integrations (#​13873)
  • fix(nuxt): Create declaration files for Nuxt module (#​13909)
  • fix(replay): Ensure replay_id is removed from frozen DSC when stopped (#​13893)
  • fix(replay): Try/catch sendBufferedReplayOrFlush to prevent cycles (#​13900)
  • fix(sveltekit): Ensure trace meta tags are always injected (#​13231)
  • fix(sveltekit): Update wrapServerRouteWithSentry to respect ParamMatchers (#​13390)
  • fix(wasm): Integration wasm uncaught WebAssembly.Exception (#​13787) (#​13854)
  • ref(nextjs): Ignore sentry spans based on query param attribute (#​13905)
  • ref(utils): Move vercelWaitUntil to utils (#​13891)

Work in this release was contributed by @​trzeciak, @​gurpreetatwal, @​ykzts and @​lizhiyao. Thank you for your contributions!

v8.33.1

Compare Source

  • fix(core): Update trpc middleware types (#​13859)
  • fix(fetch): Fix memory leak when handling endless streaming (#​13809)

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

v8.33.0

Compare Source

Important Changes
  • feat(nextjs): Support new async APIs (headers(), params, searchParams) (#​13828)

Adds support for new dynamic Next.js APIs.

  • feat(node): Add lru-memoizer instrumentation (#​13796)

Adds integration for lru-memoizer using @​opentelemetry/instrumentation-lru-memoizer.

  • feat(nuxt): Add unstable_sentryBundlerPluginOptions to module options (#​13811)

Allows passing other options from the bundler plugins (vite and rollup) to Nuxt module options.

Other Changes
  • fix(browser): Ensure wrap() only returns functions (#​13838)
  • fix(core): Adapt trpc middleware input attachment (#​13831)
  • fix(core): Don't return trace data in getTraceData and getTraceMetaTags if SDK is disabled (#​13760)
  • fix(nuxt): Don't restrict source map assets upload (#​13800)
  • fix(nuxt): Use absolute path for client config (#​13798)
  • fix(replay): Stop global event handling for paused replays (#​13815)
  • fix(sveltekit): add url param to source map upload options (#​13812)
  • fix(types): Add jsdocs to cron types (#​13776)
  • fix(nextjs): Loosen @​sentry/nextjs webpack peer dependency (#​13826)

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

v8.32.0

Compare Source

Important Changes
  • ref(browser): Move navigation span descriptions into op (#​13527)

Moves the description of navigation related browser spans into the op, e.g. browser - cache -> browser.cache and sets the description to the performanceEntry objects' names (in this context it is the URL of the page).

  • feat(node): Add amqplibIntegration (#​13714)

  • feat(nestjs): Add SentryGlobalGenericFilter and allow specifying application ref in global filter (#​13673)

Adds a SentryGlobalGenericFilter that filters both graphql and http exceptions depending on the context.

  • feat: Set log level for Fetch/XHR breadcrumbs based on status code (#​13711)

Sets log levels in breadcrumbs for 5xx to error and 4xx to warning.

Other Changes
  • chore(nextjs): Bump rollup to 3.29.5 (#​13761)
  • fix(core): Remove sampled flag from dynamic sampling context in Tracing without Performance mode (#​13753)
  • fix(node): Ensure node-fetch does not emit spans without tracing (#​13765)
  • fix(nuxt): Use Nuxt error hooks instead of errorHandler to prevent 500 (#​13748)
  • fix(test): Unflake LCP test (#​13741)

Work in this release was contributed by @​Zen-cronic and @​Sjoertjuh. Thank you for your contributions!

v8.31.0

Compare Source

Important Changes
  • feat(node): Add dataloader integration (#​13664)

This release adds a new integration for the dataloader package. The Node SDK (and all SDKs that depend on it) will now automatically instrument dataloader instances. You can also add it manually:

Sentry.init({
  integrations: [Sentry.dataloaderIntegration()],
});
Other Changes
  • feat(browser): Add navigation activationStart timestamp to pageload span (#​13658)
  • feat(gatsby): Add optional deleteSourcemapsAfterUpload (#​13610)
  • feat(nextjs): Give app router prefetch requests a http.server.prefetch op (#​13600)
  • feat(nextjs): Improve Next.js serverside span data quality (#​13652)
  • feat(node): Add disableInstrumentationWarnings option (#​13693)
  • feat(nuxt): Adding experimental_basicServerTracing option to Nuxt module (#​13643)
  • feat(nuxt): Improve logs about adding Node option 'import' (#​13726)
  • feat(replay): Add onError callback + other small improvements to debugging (#​13721)
  • feat(replay): Add experimental option to allow for a checkout every 6 minutes (#​13069)
  • feat(wasm): Unconditionally parse instruction addresses (#​13655)
  • fix: Ensure all logs are wrapped with consoleSandbox (#​13690)
  • fix(browser): Try multiple options for lazyLoadIntegration script parent element lookup (#​13717)
  • fix(feedback): Actor color applies to feedback icon (#​13702)
  • fix(feedback): Fix form width on mobile devices (#​13068)
  • fix(nestjs): Preserve original function name on SentryTraced functions (#​13684)
  • fix(node): Don't overwrite local variables for re-thrown errors (#​13644)
  • fix(normalize): Treat Infinity as NaN both are non-serializable numbers (#​13406)
  • fix(nuxt): Use correct server output file path (#​13725)
  • fix(opentelemetry): Always use active span in Propagator.inject (#​13381)
  • fix(replay): Fixes potential out-of-order segments (#​13609)

Work in this release was contributed by @​KyGuy2002, @​artzhookov, and @​julianCast. Thank you for your contributions!

v8.30.0

Compare Source

Important Changes
  • feat(node): Add kafkajs integration (#​13528)

This release adds a new integration that instruments kafkajs library with spans and traces. This integration is automatically enabled by default, but can be included with the Sentry.kafkaIntegration() import.

Sentry.init({
  integrations: [Sentry.kafkaIntegration()],
});
Other Changes
  • feat(core): Allow adding measurements without global client (#​13612)
  • feat(deps): Bump @​opentelemetry/instrumentation-undici from 0.5.0 to 0.6.0 (#​13622)
  • feat(deps): Bump @​sentry/cli from 2.33.0 to 2.35.0 (#​13624)
  • feat(node): Use @opentelemetry/instrumentation-undici for fetch tracing (#​13485)
  • feat(nuxt): Add server config to root folder (#​13583)
  • feat(otel): Upgrade @​opentelemetry/semantic-conventions to 1.26.0 (#​13631)
  • fix(browser): check supportedEntryTypes before caling the function (#​13541)
  • fix(browser): Ensure Standalone CLS span timestamps are correct (#​13649)
  • fix(nextjs): Widen removal of 404 transactions (#​13628)
  • fix(node): Remove ambiguity and race conditions when matching local variables to exceptions (#​13501)
  • fix(node): Update OpenTelemetry instrumentation package for solidstart and opentelemetry (#​13640)
  • fix(node): Update OpenTelemetry instrumentation package for solidstart and opentelemetry (#​13642)
  • fix(vue): Ensure Vue trackComponents list matches components with or without <> (#​13543)
  • ref(profiling): Conditionally shim cjs globals (#​13267)

Work in this release was contributed by @​Zen-cronic and @​odanado. Thank you for your contributions!

v8.29.0

Compare Source

Important Changes
  • Beta releases of official Solid and SolidStart Sentry SDKs

This release marks the beta releases of the @sentry/solid and @sentry/solidstart Sentry SDKs. For details on how to use them, check out the Sentry Solid SDK README and the Sentry SolidStart SDK README respectively. Please reach out on GitHub if you have any feedback or concerns.

  • feat(node): Option to only wrap instrumented modules (#​13139)

Adds the SDK option to only wrap ES modules with import-in-the-middle that specifically need to be instrumented.

import * as Sentry from '@&#8203;sentry/node';

Sentry.init({
  dsn: '__PUBLIC_DSN__',
  registerEsmLoaderHooks: { onlyIncludeInstrumentedModules: true },
});
  • feat(node): Update OpenTelemetry packages to instrumentation v0.53.0 (#​13587)

All internal OpenTelemetry instrumentation was updated to their latest version. This adds support for Mongoose v7 and v8 and fixes various bugs related to ESM mode.

Other Changes
  • feat(nextjs): Emit warning when using turbopack (#​13566)
  • feat(nextjs): Future-proof Next.js config options overriding (#​13586)
  • feat(node): Add generic-pool integration (#​13465)
  • feat(nuxt): Upload sourcemaps generated by Nitro (#​13382)
  • feat(solidstart): Add browserTracingIntegration by default (#​13561)
  • feat(solidstart): Add sentrySolidStartVite plugin to simplify source maps upload (#​13493)
  • feat(vue): Only start UI spans if parent is available (#​13568)
  • fix(cloudflare): Guard context.waitUntil call in request handler (#​13549)
  • fix(gatsby): Fix assets path for sourcemaps upload (#​13592)
  • fix(nextjs): Use posix paths for sourcemap uploads (#​13603)
  • fix(node-fetch): Use stringified origin url (#​13581)
  • fix(node): Replace dashes in generic-pool span origins with underscores (#​13579)
  • fix(replay): Fix types in WebVitalData (#​13573)
  • fix(replay): Improve replay web vital types (#​13602)
  • fix(utils): Keep logger on carrier (#​13570)

Work in this release was contributed by @​Zen-cronic. Thank you for your contribution!

v8.28.0

Compare Source

Important Changes
  • Beta release of official NestJS SDK

This release contains the beta version of @sentry/nestjs! For details on how to use it, check out the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

  • fix(browser): Remove faulty LCP, FCP and FP normalization logic (#​13502)

This release fixes a bug in the @sentry/browser package and all SDKs depending on this package (e.g. @sentry/react or @sentry/nextjs) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDK previously incorrectly processed the original values as they were reported from the browser. When updating your SDK to this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were smaller than the actually measured values. We apologize for the inconvenience!

Other Changes
  • feat(nestjs): Add SentryGlobalGraphQLFilter (#​13545)
  • feat(nestjs): Automatic instrumentation of nestjs interceptors after route execution (#​13264)
  • feat(nextjs): Add bundleSizeOptimizations to build options (#​13323)
  • feat(nextjs): Stabilize captureRequestError (#​13550)
  • feat(nuxt): Wrap config in nuxt context (#​13457)
  • feat(profiling): Expose profiler as top level primitive (#​13512)
  • feat(replay): Add layout shift to CLS replay data (#​13386)
  • feat(replay): Upgrade rrweb packages to 2.26.0 (#​13483)
  • fix(cdn): Do not mangle _metadata (#​13426)
  • fix(cdn): Fix SDK source for CDN bundles (#​13475)
  • fix(nestjs): Check arguments before instrumenting with @Injectable (#​13544)
  • fix(nestjs): Ensure exception and host are correctly passed on when using @​WithSentry (#​13564)
  • fix(node): Suppress tracing for transport request execution rather than transport creation (#​13491)
  • fix(replay): Consider more things as DOM mutations for dead clicks (#​13518)
  • fix(vue): Correctly obtain component name (#​13484)

Work in this release was contributed by @​leopoldkristjansson, @​mhuggins and @​filips123. Thank you for your contributions!

v8.27.0

Compare Source

Important Changes

  • fix(nestjs): Exception filters in main app module are not being executed (#​13278)

    With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

Other Changes
  • feat: Add options for passing nonces to feedback integration (#​13347)
  • feat: Add support for SENTRY_SPOTLIGHT env var in Node (#​13325)
  • feat(deps): bump @​prisma/instrumentation from 5.17.0 to 5.18.0 (#​13327)
  • feat(feedback): Improve error message for 403 errors (#​13441)
  • fix(deno): Don't rely on Deno.permissions.querySync (#​13378)
  • fix(replay): Ensure we publish replay CDN bundles (#​13437)

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

v8.26.0

Compare Source

Important Changes

  • feat(node): Add fsInstrumentation (#​13291)

    This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

    This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure via options whether to include path arguments or error messages as span attributes when an fs call fails:

    Sentry.init({
  integrations: [
    Sentry.fsIntegration({
      recordFilePaths: true,
      recordErrorMessagesAsSpanAttributes: true,
    }),
  ],
});

    WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.

Other Changes

  • feat(browser): Add spotlightBrowser integration (#​13263)

  • feat(browser): Allow sentry in safari extension background page (#​13209)

  • feat(browser): Send CLS as standalone span (experimental) (#​13056)

  • feat(core): Add OpenTelemetry-specific getTraceData implementation (#​13281)

  • feat(nextjs): Always add browserTracingIntegration (#​13324)

  • feat(nextjs): Always transmit trace data to the client (#​13337)

  • feat(nextjs): export SentryBuildOptions (#​13296)

  • feat(nextjs): Update experimental_captureRequestError to reflect RequestInfo.path change in Next.js canary (#​13344)

  • feat(nuxt): Always add tracing meta tags (#​13273)

  • feat(nuxt): Set transaction name for server error (#​13292)

  • feat(replay): Add a replay-specific logger (#​13256)

  • feat(sveltekit): Add bundle size optimizations to plugin options (#​13318)

  • feat(sveltekit): Always add browserTracingIntegration (#​13322)

  • feat(tracing): Make long animation frames opt-out (#​13255)

  • fix(astro): Correctly extract request data (#​13315)

  • fix(astro): Only track access request headers in dynamic page requests (#​13306)

  • fix(nuxt): Add import line for disabled autoImport (#​13342)

  • fix(nuxt): Add vue to excludeEsmLoaderHooks array (#​13346)

  • fix(opentelemetry): Do not overwrite http span name if kind is internal (#​13282)

  • fix(remix): Ensure origin is correctly set for remix server spans (#​13305)

Work in this release was contributed by @​MonstraG, @​undead-voron and @​Zen-cronic. Thank you for your contributions!

v8.25.0

Compare Source

Important Changes
  • Alpha release of Official Solid Start SDK

This release contains the alpha version of @sentry/solidstart, our SDK for Solid Start! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

Other Changes
  • feat(astro): Add bundleSizeOptimizations vite options to integration (#​13250)
  • feat(astro): Always add BrowserTracing (#​13244)
  • feat(core): Add getTraceMetaTags function (#​13201)
  • feat(nestjs): Automatic instrumentation of nestjs exception filters (#​13230)
  • feat(node): Add useOperationNameForRootSpan tographqlIntegration (#​13248)
  • feat(sveltekit): Add wrapServerRouteWithSentry wrapper (#​13247)
  • fix(aws-serverless): Extract sentry trace data from handler context over event (#​13266)
  • fix(browser): Initialize default integration if defaultIntegrations: undefined (#​13261)
  • fix(utils): Streamline IP capturing on incoming requests (#​13272)

v8.24.0

Compare Source

  • feat(nestjs): Filter RPC exceptions (#​13227)
  • fix: Guard getReader function for other fetch implementations (#​13246)
  • fix(feedback): Ensure feedback can be lazy loaded in CDN bundles (#​13241)

v8.23.0

Compare Source

Important Changes
  • feat(cloudflare): Add Cloudflare D1 instrumentation (#​13142)

This release includes support for Cloudflare D1, Cloudflare's serverless SQL database. To instrument your Cloudflare D1 database, use the instrumentD1WithSentry method as follows:

// env.DB is the D1 DB binding configured in your `wrangler.toml`
const db = instrumentD1WithSentry(env.DB);
// Now you can use the database as usual
await db.prepare('SELECT * FROM table WHERE id = ?').bind(1).run();
Other Changes
  • feat(cloudflare): Allow users to pass handler to sentryPagesPlugin (#​13192)
  • feat(cloudflare): Instrument scheduled handler (#​13114)
  • feat(core): Add getTraceData function (#​13134)
  • feat(nestjs): Automatic instrumentation of nestjs interceptors before route execution (#​13153)
  • feat(nestjs): Automatic instrumentation of nestjs pipes (#​13137)
  • feat(nuxt): Filter out Nuxt build assets (#​13148)
  • feat(profiling): Attach sdk info to chunks (#​13145)
  • feat(solidstart): Add sentry onBeforeResponse middleware to enable distributed tracing (#​13221)
  • feat(solidstart): Filter out low quality transactions for build assets (#​13222)
  • fix(browser): Avoid showing browser extension error message in non-window global scopes (#​13156)
  • fix(feedback): Call dialog.close() in dialog close callbacks in \_loadAndRenderDialog (#​13203)
  • fix(nestjs): Inline Observable type to resolve missing 'rxjs' dependency (#​13166)
  • fix(nuxt): Detect pageload by adding flag in Vue router (#​13171)
  • fix(utils): Handle when requests get aborted in fetch instrumentation (#​13202)
  • ref(browser): Improve browserMetrics collection (#​13062)

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

v8.22.0

Compare Source

Important Changes
  • feat(cloudflare): Add plugin for cloudflare pages (#​13123)

This release adds support for Cloudflare Pages to @sentry/cloudflare, our SDK for the Cloudflare Workers JavaScript Runtime! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

// functions/_middleware.js
import * as Sentry from '@&#8203;sentry/cloudflare';

export const onRequest = Sentry.sentryPagesPlugin({
  dsn: __PUBLIC_DSN__,
  // Set tracesSampleRate to 1.0 to capture 100% of spans for tracing.
  tracesSampleRate: 1.0,
});
Other Changes
  • feat(meta-sdks): Remove runtime tags (#​13105)
  • feat(nestjs): Automatic instrumentation of nestjs guards (#​13129)
  • feat(nestjs): Filter all HttpExceptions (#​13120)
  • feat(replay): Capture exception when internal_sdk_error client report happens (#​13072)
  • fix: Use globalThis for code injection (#​13132)

v8.21.0

Compare Source

Important Changes
  • Alpha release of Official Cloudflare SDK
    • feat(cloudflare): Add withSentry method (#​13025)
    • feat(cloudflare): Add cloudflare sdk scaffolding (#​12953)
    • feat(cloudflare): Add basic cloudflare package and tests (#​12861)

This release contains the alpha version of @sentry/cloudflare, our SDK for the Cloudflare Workers JavaScript Runtime! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

Please note that only Cloudflare Workers are tested and supported - official Cloudflare Pages support will come in an upcoming release.

Other Changes
  • feat(feedback): Make cropped screenshot area draggable (#​13071)
  • feat(core): Adapt spans for client-side fetch to streaming responses (#​12723)
  • feat(core): Capture # of dropped spans through beforeSendTransaction (#​13022)
  • feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.43.0 to 0.43.1 (#​13089)
  • feat(deps): bump @opentelemetry/instrumentation-express from 0.41.0 to 0.41.1 (#​13090)
  • feat(nestjs): Automatic instrumentation of nestjs middleware (#​13065)
  • feat(node): Upgrade import-in-the-middle to 1.11.0 (#​13107)
  • feat(nuxt): Add connected tracing meta tags (#​13098)
  • feat(nuxt): Add vue-router instrumentation (#​13054)
  • feat(solidstart): Add server action instrumentation helper (#​13035)
  • fix(feedback): Ensure pluggable feedback CDN bundle is correctly built (#​13081)
  • fix(nextjs): Only delete clientside bundle source maps with sourcemaps.deleteFilesAfterUpload (#​13102)
  • fix(node): Improve OTEL validation logic (#​13079)

v8.20.0

Compare Source

Important Changes
  • feat(node): Allow to pass registerEsmLoaderHooks to preload (#​12998)

You can write your own custom preload script and configure this in the preload options. registerEsmLoaderHooks can be passed as an option to preloadOpenTelemetry, which allows to exclude/include packages in the preload.

  • fix(node): Do not emit fetch spans when tracing is disabled (#​13003)

Sentry will not emit "fetch" spans if tracing is disabled. This is relevant for user who use their own sampler.

Other Changes
  • feat(feedback): Trigger button aria label configuration (#​13008)
  • feat(nestjs): Change nest sdk setup (#​12920)
  • feat(node): Extend ESM hooks options for iitm v1.10.0 (#​13016)
  • feat(node): Send client reports (#​12951)
  • feat(nuxt): Automatically add BrowserTracing (#​13005)
  • feat(nuxt): Setup source maps with vite config (#​13018)
  • feat(replay): Improve public Replay APIs (#​13000)

v8.19.0

Compare Source

node --import=@​sentry/node/import app.js


- **feat(node): Do not exit process by default when other `onUncaughtException` handlers are registered in
  `onUncaughtExceptionIntegration` (#&#8203;11532)**

In v8, we will no longer exit the node process by default if other uncaught exception handlers have been registered by
the user.

- **Better handling of transaction name for errors**

We improved the way we keep the transaction name for error events, even when spans are not sampled or performance is
disabled.

- feat(fastify): Update scope `transactionName` when handling request (#&#8203;11447)
- feat(hapi): Update scope `transactionName` when handling request (#&#8203;11448)
- feat(koa): Update scope `transactionName` when creating router span (#&#8203;11476)
- feat(sveltekit): Update scope transactionName when handling server-side request (#&#8203;11511)
- feat(nestjs): Update scope transaction name with parameterized route (#&#8203;11510)

##### Removal/Refactoring of deprecated functionality

- feat(core): Remove `getCurrentHub` from `AsyncContextStrategy` (#&#8203;11581)
- feat(core): Remove `getGlobalHub` export (#&#8203;11565)
- feat(core): Remove `Hub` class export (#&#8203;11560)
- feat(core): Remove most Hub class exports (#&#8203;11536)
- feat(nextjs): Remove webpack 4 support (#&#8203;11605)
- feat(vercel-edge): Stop using hub (#&#8203;11539)

##### Other Changes

- feat: Hoist `getCurrentHub` shim to core as `getCurrentHubShim` (#&#8203;11537)
- feat(core): Add default behaviour for `rewriteFramesIntegration` in browser (#&#8203;11535)
- feat(core): Ensure replay envelopes are sent in order when offline (#&#8203;11413)
- feat(core): Extract errors from props in unkown inputs (#&#8203;11526)
- feat(core): Update metric normalization (#&#8203;11518)
- feat(feedback): Customize feedback placeholder text color (#&#8203;11417)
- feat(feedback): Maintain v7 compat in the @&#8203;sentry-internal/feedback package (#&#8203;11461)
- feat(next): Handle existing root spans for isolation scope (#&#8203;11479)
- feat(node): Ensure tracing without performance (TWP) works (#&#8203;11564)
- feat(opentelemetry): Export `getRequestSpanData` (#&#8203;11508)
- feat(opentelemetry): Remove otel.attributes in context (#&#8203;11604)
- feat(ratelimit): Add metrics rate limit (#&#8203;11538)
- feat(remix): Skip span creation for `OPTIONS` and `HEAD` requests. (#&#8203;11149)
- feat(replay): Merge packages together & ensure bundles are built (#&#8203;11552)
- feat(tracing): Adds span envelope and datacategory (#&#8203;11534)
- fix(browser): Ensure pageload trace remains active after pageload span finished (#&#8203;11600)
- fix(browser): Ensure tracing without performance (TWP) works (#&#8203;11561)
- fix(nextjs): Fix `tunnelRoute` matching logic for hybrid cloud (#&#8203;11576)
- fix(nextjs): Remove Http integration from Next.js (#&#8203;11304)
- fix(node): Ensure isolation scope is correctly cloned for non-recording spans (#&#8203;11503)
- fix(node): Make fastify types more broad (#&#8203;11544)
- fix(node): Send ANR events without scope if event loop blocked indefinitely (#&#8203;11578)
- fix(tracing): Fixes latest route name and source not updating correctly (#&#8203;11533)
- ref(browser): Move browserTracing into browser pkg (#&#8203;11484)
- ref(feedback): Configure font size (#&#8203;11437)
- ref(feedback): Refactor Feedback types into @&#8203;sentry/types and reduce the exported surface area (#&#8203;11355)

#### 8.0.0-beta.0

This release failed to publish correctly. Use 8.0.0-beta.1 instead.

#### 8.0.0-alpha.9

This is the eighth alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.

Read the [in-depth migration guide](./MIGRATION.md) to find out how to address any breaking changes in your code.

##### Important Changes

- **feat: Add @&#8203;sentry-internal/browser-utils (#&#8203;11381)**

A big part of the browser-runtime specific exports of the internal `@sentry/utils` package were moved into a new package
`@sentry-internal/browser-utils`. If you imported any API from `@sentry/utils` (which is generally not recommended but
necessary for some workarounds), please check that your import statements still point to existing exports after
upgrading.

- **feat: Add loader file to node-based SDKs to support ESM monkeypatching (#&#8203;11338)**

When using ESM, it is necessary to use a "loader" to be able to instrument certain third-party packages and Node.js API.
The server-side SDKs now ship with a set of ESM loader hooks, that should be used when using ESM. Use them as follows:

```sh

v8.18.0

Compare Source

Important Changes
  • ref: Deprecate enableTracing (12897)

The enableTracing option has been deprecated and will be removed in the next major version. We recommend removing it in favor of the tracesSampleRate and tracesSampler options. If you want to enable performance monitoring, please set the tracesSampleRate to a sample rate of your choice, or provide a sampling function as tracesSampler option instead. If you want to disable performance monitoring, remove the tracesSampler and tracesSampleRate options.

Other Changes
  • feat(node): Expose exclude and include options for ESM loader (#​12910)
  • feat(browser): Add user agent to INP standalone span attributes (#​12896)
  • feat(nextjs): Add experimental_captureRequestError for onRequestError hook (#​12885)
  • feat(replay): Bump rrweb to 2.25.0 (#​12478)
  • feat(tracing): Add long animation frame tracing (#​12646)
  • fix: Cleanup hooks when they are not used anymore (#​12852)
  • fix(angular): Guard ErrorEvent check in ErrorHandler to avoid throwing in Node environments (#​12892)
  • fix(inp): Ensure INP spans have correct transaction (#​12871)
  • fix(nestjs): Do not make SentryTraced() decorated functions async (#​12879)
  • fix(nextjs): Support automatic instrumentation for app directory with custom page extensions (#​12858)
  • fix(node): Ensure correct URL is passed to ignoreIncomingRequests callback (#​12929)
  • fix(otel): Do not add otel.kind: INTERNAL attribute (#​12841)
  • fix(solidstart): Set proper sentry origin for solid router integration when used in solidstart sdk (#​12919)
  • fix(sveltekit): Add Vite peer dep for proper type resolution (#​12926)
  • fix(tracing): Ensure you can pass null as parentSpan in startSpan* (#​12928)
  • ref(core): Small bundle size improvement (#​12830)

Work in this release was contributed by @​GitSquared, @​ziyadkhalil and @​mcous. Thank you for your contributions!

v8.17.0

Compare Source

  • feat: Upgrade OTEL deps (#​12809)
  • fix(nuxt): Add module to build:transpile script (#​12843)
  • fix(browser): Allow SDK initialization in NW.js apps (#​12846)

v8.16.0

Compare Source

Important Changes
  • feat(nextjs): Use spans generated by Next.js for App Router (#​12729)

Previously, the @sentry/nextjs SDK automatically recorded spans in the form of transactions for each of your top-level server components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have a root span, and more importantly, if you had data stream to the client, its duration was not captured because the server component spans had finished before the data could finish streaming.

With this release, we will capture the duration of App Router requests in their entirety as a single transaction with server component spans being descendants of that transaction. This means you will get more data that is also more accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it has before.

Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no longer receive server component transactions like Page Server Component (/path/to/route) (unless using the Edge runtime), and you will instead receive transactions for your App Router SSR requests that look like GET /path/to/route.

If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.

  • - feat(nestjs): Add nest cron monitoring support (#​12781)

The @sentry/nestjs SDK now includes a @SentryCron decorator that can be used to augment the native NestJS @Cron decorator to send check-ins to Sentry before and after each cron job run:

import { Cron } from '@&#8203;nestjs/schedule';
import { SentryCron, MonitorConfig } from '@&#8203;sentry/nestjs';
import type { MonitorConfig } from '@&#8203;sentry/types';

const monitorConfig: MonitorConfig = {
  schedule: {
    type: 'crontab',
    value: '* * * * *',
  },
  checkinMargin: 2, // In minutes. Optional.
  maxRuntime: 10, // In minutes. Optional.
  timezone: 'America/Los_Angeles', // Optional.
};

export class MyCronService {
  @&#8203;Cron('* * * * *')
  @&#8203;SentryCron('my-monitor-slug', monitorConfig)
  handleCron() {
    // Your cron job logic here
  }
}
Other Changes
  • feat(node): Allow to pass instrumentation config to httpIntegration (#​12761)
  • feat(nuxt): Add server error hook (#​12796)
  • feat(nuxt): Inject sentry config with Nuxt addPluginTemplate (#​12760)
  • fix: Apply stack frame metadata before event processors (#​12799)
  • fix(feedback): Add missing h import in ScreenshotEditor (#​12784)
  • fix(node): Ensure autoSessionTracking is enabled by default (#​12790)
  • ref(feedback): Let CropCorner inherit the existing h prop (#​12814)
  • ref(otel): Ensure we never swallow args for ContextManager (#​12798)

v8.15.0

Compare Source

  • feat(core): allow unregistering callback through on (#​11710)
  • feat(nestjs): Add function-level span decorator to nestjs (#​12721)
  • feat(otel): Export & use spanTimeInputToSeconds for otel span exporter (#​12699)
  • fix(core): Pass origin as referrer for lazyLoadIntegration (#​12766)
  • fix(deno): Publish from build directory (#​12773)
  • fix(hapi): Specify error channel to filter boom errors (#​12725)
  • fix(react): Revert back to jsxRuntime: 'classic' to prevent breaking react 17 (#​12775)
  • fix(tracing): Report dropped spans for transactions (#​12751)
  • ref(scope): Delete unused public getStack() (#​12737)

Work in this release was contributed by @​arturovt and @​jaulz. Thank you for your contributions!

v8.14.0

Compare Source

Important Changes
  • feat(nestjs): Filter 4xx errors (#​12695)

The @sentry/nestjs SDK no longer captures 4xx errors automatically.

Other Changes

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

v8.13.0

Compare Source

Important Changes
  • feat(nestjs): Add Nest SDK This release adds a dedicated SDK for NestJS (@sentry/nestjs) in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (@sentry/node) supporting the same set of features. See the docs for how to use the SDK.
Other Changes

v8.12.0

Compare Source

Important Changes
  • feat(solid): Remove need to pass router hooks to solid integration (breaking)

This release introduces breaking changes to the @sentry/solid package (which is currently out in alpha).

We've made it easier to get started with the solid router integration by removing the need to pass use* hooks explicitly to solidRouterBrowserTracingIntegration. Import solidRouterBrowserTracingIntegration from @sentry/solid/solidrouter and add it to Sentry.init

import * as Sentry from '@&#8203;sentry/solid';
import { solidRouterBrowserTracingIntegration, withSentryRouterRouting } from '@&#8203;sentry/solid/solidrouter';
import { Router } from '@&#8203;solidjs/router';

Sentry.init({
  dsn: '__PUBLIC_DSN__',
  integrations: [solidRouterBrowserTracingIntegration()],
  tracesSampleRate: 1.0, //  Capture 100% of the transactions
});

const SentryRouter = withSentryRouterRouting(Router);
  • feat(core): Return client from init method (#​12585)

Sentry.init() now returns a client directly, so you don't need to explicitly call getClient() anymore:

const client = Sentry.init();
  • feat(nextjs): Add deleteSourcemapsAfterUpload option (#​12457)

This adds an easy way to delete sourcemaps immediately after uploading them:

module.exports = withSentryConfig(nextConfig, {
  sourcemaps: {
    deleteSourcemapsAfterUpload: true,
  },
});
  • feat(node): Allow to configure maxSpanWaitDuration (#​12610)

Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However, if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early. In this case, you can increase this duration to a value that fits your expected data.

Other Changes
  • feat(feedback): Extra check for iPad in screenshot support (#​12593)
  • fix(bundle): Ensure CDN bundles do not overwrite window.Sentry (#​12580)
  • fix(feedback): Inject preact from feedbackModal into feedbackScreenshot integration (#​12535)
  • fix(node): Re-throw errors from koa middleware (#​12609)
  • fix(remix): Mark isRemixV2 as optional in exposed types. (#​12614)
  • ref(node): Add error message to NodeFetch log (#​12612)

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

v8.11.0

Compare Source

Important Changes
  • feat(core): Add parentSpan option to startSpan* APIs (#​12567)

We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to explicitly manage the parent-child relationship of your spans better.

Sentry.startSpan({ name: 'root' }, parent => {
  const span = Sentry.startInactiveSpan({ name: 'xxx', parentSpan: parent });

  Sentry.startSpan({ name: 'xxx', parentSpan: parent }, () => {});

  Sentry.startSpanManual({ name: 'xxx', parentSpan: parent }, () => {});
});
Other Changes
  • feat(node): Detect release from more providers (#​12529)
  • fix(profiling-node): Use correct getGlobalScope import (#​12564)
  • fix(profiling-node) sample timestamps need to be in seconds (#​12563)
  • ref: Align @sentry/node exports from framework SDKs. (#​12589)

v8.10.0

Compare Source

Important Changes
  • feat(remix): Migrate to opentelemetry-instrumentation-remix. (#​12110)

You can now simplify your remix instrumentation by opting-in like this:

const Sentry = require('@&#8203;sentry/remix');

Sentry.init({
  dsn: YOUR_DSN
  // opt-in to new auto instrumentation
  autoInstrumentRemix: true,
});

With this setup, you do not need to add e.g. wrapExpressCreateRequestHandler anymore. Additionally, the quality of the captured data improves. The old way to use @sentry/remix continues to work, but it is encouraged to use the new setup.

Other Changes
  • feat(browser): Export thirdPartyErrorFilterIntegration from @sentry/browser (#​12512)
  • feat(feedback): Allow passing tags field to any feedback config param (#​12197)
  • feat(feedback): Improve screenshot quality for retina displays (#​12487)
  • feat(feedback): Screenshots don't resize after cropping (#​12481)
  • feat(node) add max lineno and colno limits (#​12514)
  • feat(profiling) add global profile context while profiler is running (#​12394)
  • feat(react): Add React version to events (#​12390)
  • feat(replay): Add url to replay hydration error breadcrumb type (#​12521)
  • fix(core): Ensure standalone spans respect sampled flag (#​12533)
  • fix(core): Use maxValueLength in extra error data integration (#​12174)
  • fix(feedback): Fix scrolling after feedback submission (#​12499)
  • fix(feedback): Send feedback rejects invalid responses (#​12518)
  • fix(nextjs): Update @​rollup/plugin-commonjs (#​12527)
  • fix(node): Ensure status is correct for http server span errors (#​12477)
  • fix(node): UnifygetDynamicSamplingContextFromSpan (#​12522)
  • fix(profiling): continuous profile chunks should be in seconds (#​12532)
  • fix(remix): Add nativeFetch support for accessing request headers (#​12479)
  • fix(remix): Export no-op as captureRemixServerException from client SDK (#​12497)
  • ref(node) refactor contextlines to use readline (#​12221)

Work in this release was contributed by @​AndreyKovanov and @​kiliman. Thank you for your contributions!

v8.9.2

Compare Source

  • fix(profiling): Update exports so types generate properly (#​12469)

v8.9.1

Important changes

  • feat(solid): Add Solid SDK

    This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for Solid Router and a custom ErrorBoundary. See the package README for how to use the SDK.

Other changes

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

v8.9.0

This release failed to publish correctly, please use 8.9.1 instead.

v8.8.0

Compare Source

  • feat: Upgrade OTEL dependencies (#​12388)

This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use import-in-the-middle v1.8.0. This should fix numerous issues with using OTEL instrumentation with ESM.

High level issues fixed with OTEL + ESM:

  • incompatibilities with using multiple loaders, commonly encountered while using tsx or similar libraries.
  • incompatibilities with libraries that use duplicate namespace exports like date-fns.
  • incompatibilities with libraries that use self-referencing namespace imports like openai.
  • incompatibilities with dynamic export patterns like exports with function calls.
  • ENOENT: no such file or directory bugs that libraries like discord.js surface.

If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.

  • deps: Bump Sentry bundler plugins to version 2.18.0 (#​12381)
  • feat: Add thirdPartyErrorFilterIntegration (#​12267)
  • feat(core): Filter out error events with exception values and no stacktraces, values, or types (#​12387)
  • feat(core): Ignore additional common but inactionable errors (#​12384)
  • feat(deps): Bump @​opentelemetry/propagator-aws-xray from 1.3.1 to 1.24.1 (#​12333)
  • feat(deps): Bump @​sentry/cli from 2.31.2 to 2.32.1 (#​12332)
  • feat(redis): Support mget command in caching functionality (#​12380)
  • feat(vercel-edge): Export core integrations from Vercel edge SDK (#​12308)
  • fix(browser): Fix idle span ending (#​12306)
  • fix(browser): Fix parenthesis parsing logic for chromium (#​12373)
  • fix(browser): Fix types export path for CJS (#​12305)
  • fix(feedback): Override TriggerLabel Option (#​12316)
  • fix(feedback): Wait for document to be ready before doing autoinject (#​12294)
  • fix(nextjs): Fix memory leak (#​12335)
  • fix(nextjs): Fix version detection and option insertion logic for clientTraceMetadata option (#​12323)
  • fix(nextjs): Update argument name in log message about sentry property on Next.js config object (#​12366)
  • fix(node): Do not manually finish / update root Hapi spans. (#​12287)
  • fix(node): Fix virtual parent span ID handling & update create-next-app E2E test (#​12368)
  • fix(node): Skip capturing Hapi Boom responses v8. (#​12288)
  • fix(performance): Fix LCP not getting picked up on initial pageload transaction by setting reportAllChanges to true (#​12360)
  • fix(replay): Avoid infinite loop of logs (#​12309)
  • fix(replay): Ignore old events when manually starting replay (#​12349)
  • ref(browser): Ensure idle span ending is consistent (#​12310)
  • ref(profiling): unref timer (#​12340)

Work in this release contributed by @​dohooo, @​mohd-akram, and @​ykzts. Thank you for your contributions!

v8.7.0

Important Changes

  • feat(react): Add TanStack Router integration (#​12095)

    This release adds instrumentation for TanStack router with a new tanstackRouterBrowserTracingIntegration in the @sentry/react SDK:

    import * as Sentry from '@&#8203;sentry/react';
import { createRouter } from '@&#8203;tanstack/react-router';

const router = createRouter({
  // Your router options...
});

Sentry.init({
  dsn: '___PUBLIC_DSN___',
  integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
  tracesSampleRate: 1.0,
});
Other Changes
  • fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is set (#​12278)

v8.6.0

Important Changes

  • feat(metrics): Add timings method to metrics (#​12226)

    This introduces a new method, metrics.timing(), which can be used in two ways:

    1. With a numeric value, to simplify creating a distribution metric. This will default to second as unit:
    Sentry.metrics.timing('myMetric', 100);
    1. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds:
    const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);

  • feat(react): Add Sentry.reactErrorHandler (#​12147)

    This MR introduces Sentry.reactErrorHandler, which you can use in React 19 as follows:

    import * as Sentry from '@&#8203;sentry/react';
import { hydrateRoot } from 'react-dom/client';

ReactDOM.hydrateRoot(
  document.getElementById('root'),
  <React.StrictMode>
    <App />
  </React.StrictMode>,
  {
    onUncaughtError: Sentry.reactErrorHandler(),
    onCaughtError: Sentry.reactErrorHandler((error, errorInfo) => {
      // optional callback if users want custom config.
    }),
  },
);

    For more details, take a look at the MR. Our documentation will be updated soon!

Other Changes
  • feat(sveltekit): Add request data to server-side events (#​12254)
  • fix(core): Pass in cron monitor config correctly (#​12248)
  • fix(nextjs): Don't capture suspense errors in server components (#​12261)
  • fix(tracing): Ensure sent spans are limited to 1000 (#​12252)
  • ref(core): Use versioned carrier on global object (#​12206)

v8.5.0

Compare Source

Important Changes
  • feat(react): Add React 19 to peer deps (#​12207)

This release adds support for React 19 in the @sentry/react SDK package.

  • feat(node): Add @sentry/node/preload hook (#​12213)

This release adds a new way to initialize @sentry/node, which allows you to use the SDK with performance instrumentation even if you cannot call Sentry.init() at the very start of your app.

First, run the SDK like this:

node --require @&#8203;sentry/node/preload ./app.js

Now, you can initialize and import the rest of the SDK later or asynchronously:

const express = require('express');
const Sentry = require('@&#8203;sentry/node');

const dsn = await getSentryDsn();
Sentry.init({ dsn });

For more details, head over to the MR Description of the new feature. Our docs will be updated soon with a new guide.

Other Changes
  • feat(browser): Do not include metrics in base CDN bundle (#​12230)
  • feat(core): Add startNewTrace API (#​12138)
  • feat(core): Allow to pass custom scope to captureFeedback() (#​12216)
  • feat(core): Only allow SerializedSession in session envelope items (#​11979)
  • feat(nextjs): Use Vercel's waitUntil to defer freezing of Vercel Lambdas (#​12133)
  • feat(node): Ensure manual OTEL setup works (#​12214)
  • fix(aws-serverless): Avoid minifying Module._resolveFilename in Lambda layer bundle (#​12232)
  • fix(aws-serverless): Ensure lambda layer uses default export from ImportInTheMiddle (#​12233)
  • fix(browser): Improve browser extension error message check (#​12146)
  • fix(browser): Remove optional chaining in INP code (#​12196)
  • fix(nextjs): Don't report React postpone errors (#​12194)
  • fix(nextjs): Use global scope for generic event filters (#​12205)
  • fix(node): Add origin to redis span (#​12201)
  • fix(node): Change import of @prisma/instrumentation to use default import (#​12185)
  • fix(node): Only import inspector asynchronously (#​12231)
  • fix(replay): Update matcher for hydration error detection to new React docs (#​12209)
  • ref(profiling-node): Add warning when using non-LTS node (#​12211)

v8.4.0

Compare Source

Important Changes
  • feat(nextjs): Trace pageloads in App Router (#​12157)

If you are using Next.js version 14.3.0-canary.64 or above, the Sentry Next.js SDK will now trace clientside pageloads with React Server Components. This means, that client-side errors like Error: An error occurred in the Server Components render., which previously didn't give you much information on how that error was caused, can now be traced back to a specific error in a server component.

  • feat(angular): Add Support for Angular 18 (#​12183)

This release guarantees support for Angular 18 with @sentry/angular.

Other Changes

v8.3.0

Compare Source

Important Changes
  • Better Node Framework Span Data

This release improves data quality of spans emitted by Express, Fastify, Connect, Koa, Nest.js and Hapi.

When using Sentry in ESM mode, you can now use Sentry without manually calling init like this:

 SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --import=@&#8203;sentry/node/init app.mjs

When using CommonJS, you can do:

 SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0 node --require=@&#8203;sentry/node/init app.js
Other Changes
  • chore: Align and update MIT license dates (#​12143)
  • chore: Resolve or postpone a random assortment of TODOs (#​11977)
  • doc(migration): Add entry for runWithAsyncContext (#​12153)
  • docs: Add migration docs to point out that default import does not work (#​12100)
  • docs(sveltekit): process.env.SENTRY_AUTH_TOKEN (#​12118)
  • feat(browser): Ensure browserProfilingIntegration is published to CDN (#​12158)
  • feat(google-cloud): Expose ESM build (#​12149)
  • feat(nextjs): Ignore Prisma critical dependency warnings (#​12144)
  • feat(node): Add app.free_memory info to events (#​12150)
  • feat(node): Do not create GraphQL resolver spans by default (#​12097)
  • feat(node): Use node: prefix for node built-ins (#​11895)
  • feat(replay): Use unwrapped setTimeout to avoid e.g. angular change detection (#​11924)
  • fix(core): Add dsn to span envelope header (#​12096)
  • fix(feedback): Improve feedback border color in dark-mode, and prevent auto-dark mode when a theme is picked (#​12126)
  • fix(feedback): Set optionOverrides to be optional in TS definition (#​12125)
  • fix(nextjs): Don't put undefined values in props (#​12131)
  • fix(nextjs): Fix legacy configuration method detection for emitting warning (#​12136)
  • fix(node): Ensure fetch/http breadcrumbs are created correctly (#​12137)
  • fix(node): Update @prisma/instrumentation from 5.13.0 to 5.14.0 (#​12081)
  • ref(node): Add log for running in ESM/CommonJS mode (#​12134)
  • ref(node): Handle failing hook registration gracefully (#​12135)
  • ref(node): Only show instrumentation warning when tracing is enabled (#​12141)

Work in this release contributed by @​pboling. Thank you for your contribution!

v8.2.1

Compare Source

  • fix(aws-serverless): Fix build of lambda layer (#​12083)
  • fix(nestjs): Broaden nest.js type (#​12076)

v8.2.0

Compare Source

  • feat(redis-cache): Create cache-span with prefixed keys (get/set commands) (#​12070)
  • feat(core): Add beforeSendSpan hook (#​11886)
  • feat(browser): Improve idle span handling (#​12065)
  • fix(node): Set transactionName for unsampled spans in httpIntegration (#​12071)
  • fix(core): Export Scope interface as Scope (#​12067)
  • fix(core): Avoid looking up client for hasTracingEnabled() if possible (#​12066)
  • fix(browser): Use consistent timestamps (#​12063)
  • fix(node): Fix check for performance integrations (#​12043)
  • ref(sveltekit): Warn to delete source maps if Sentry plugin enabled source maps generation (#​12072)

v8.1.0

Compare Source

This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we updated some initially missed points in our migration guides and documentation.

  • feat(aws-serverless): Fix tree-shaking for aws-serverless package (#​12017)
  • feat(node): Bump opentelemetry instrumentation to latest version (#​12028)
  • feat(scope): Bring back lastEventId on isolation scope (#​11951) (#​12022)
  • fix(aws-serverless): Export awslambda-auto
  • fix(node): Do not warn for missing instrumentation if SDK is disabled (#​12041)
  • fix(react): Set dependency-injected functions as early as possible (#​12019)
  • fix(react): Warn and fall back gracefully if dependency injected functions are not available (#​12026)
  • ref(core): Streamline parseSampleRate utility function (#​12024)
  • ref(feedback): Make eventId optional and use lastEventId in report dialog (#​12029)

v8.0.0

Compare Source

The Sentry JS SDK team is proud to announce the release of version 8.0.0 of Sentry's JavaScript SDKs - it's been a long time coming! Thanks to everyone for your patience and a special shout out to the brave souls testing preview builds and reporting issues - we appreciate your support!

How to Upgrade to Version 8:

We recommend reading the migration guide docs to find out how to address any breaking changes in your code for your specific platform or framework.

To automate upgrading to v8 as much as possible, use our migration codemod @sentry/migr8:

npx @&#8203;sentry/migr8@&#8203;latest

All deprecations from the v7 cycle, with the exception of getCurrentHub(), have been removed and can no longer be used in v8. If you have an advanced Sentry SDK setup, we additionally recommend reading the in-depth migration guide in our repo which highlights all changes with additional details and information.

The rest of this changelog highlights the most important (breaking) changes and links to more detailed information.

Version Support

With v8, we dropped support for several old runtimes and browsers

Node SDKs: The Sentry JavaScript SDK v8 now supports Node.js 14.8.0 or higher. This applies to @sentry/node and all of our node-based server-side sdks (@sentry/nextjs, @sentry/remix, etc.). Furthermore, version 8 now ships with full support for ESM-based node apps using Node.js 18.19.0 or higher.

Browser SDKs: The browser SDKs now require ES2018+ compatible browsers. New minimum browser versions:

  • Chrome 71
  • Edge 79
  • Safari 12.1, iOS Safari 12.2
  • Firefox 65
  • Opera 58
  • Samsung Internet 10

For more details, please see the version support section in our migration guide.

Initializing Server-side SDKs (Node, Bun, Deno, Serverless):

In v8, we support a lot more node-based packages than before. In order to ensure auto-instrumentation works, the SDK now needs to be imported and initialized before any other import in your code.

We recommend creating a new file (e.g. instrumentation.js) to import and initialize the SDK. Then, import the file on top of your entry file or detailed instructions, check our updated SDK setup docs initializing the SDK in v8.

Performance Monitoring Changes

The API around performance monitoring and tracing has been streamlined, and we've added support for more integrations out of the box.

Functional Integrations

Integrations are now simple functions instead of classes. Class-based integrations have been removed:

// old (v7)
Sentry.init({
  integrations: [new Sentry.BrowserTracing()],
});

// new (v8)
Sentry.init({
  integrations: [Sentry.browserTracingIntegration()],
});
Package removal

The following packages have been removed or replaced and will no longer be published:

Changes since 8.0.0-rc.3

  • feat(nextjs): Remove transpileClientSDK (#​11978)

    As we are dropping support for Internet Explorer 11 and other other older browser versions wih version 8.0.0, we are also removing the transpileClientSDK option from the Next.js SDK. If you need to support these browser versions, please configure Webpack and Next.js to down-compile the SDK.

  • feat(serverless): Do not include performance integrations by default (#​11998)

    To keep Lambda bundle size reasonable, the SDK no longer ships with all performance (database) integrations by default. Add the Sentry integrations of the databases and other tools you're using manually to your Sentry.init call by following this guide. Note that this change does not apply if you use the SDK with the Sentry AWS Lambda layer.

  • feat(feedback): Simplify public css configuration for feedback (#​11985)

  • fix(feedback): Check for empty user (#​11993)

  • fix(replay): Fix type for replayCanvasIntegration (#​11995)

  • fix(replay): Fix user activity not being updated in start() (#​12001)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Edited by Renovate Bot

Merge request reports