sentry-javascript

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

Bundle size 📦

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)

• feat(v7): Add support for global onUnhandled Error/Promise for Bun (#11959)
• fix(replay/v7): Fix user activity not being updated in start() (#12003)
• ref(api): Remove lastEventId deprecation warnings (#12042)

Bundle size 📦

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 @sentry/migr8@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 63
• Edge 79
• Safari/iOS Safari 12
• Firefox 58
• Opera 50
• Samsung Internet 8.2

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.

• Performance Monitoring API
• Performance Monitoring Integrations

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:

• @sentry/hub
• @sentry/tracing
• @sentry/integrations
• @sentry/serverless
• @sentry/replay

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)

Bundle size 📦

Important Changes

• feat(bun): Add Bun Global Unhandled Handlers (#11960)

The Bun SDK will now capture global unhandled errors.

Other Changes

• feat(node): Log process and thread info on initialisation (#11972)
• fix(aws-serverless): Include ESM artifacts in package (#11973)
• fix(browser): Only start http.client spans if there is an active parent span (#11974)
• fix(feedback): Improve CSS theme variable names and layout (#11964)
• fix(node): Ensure execArgv are not sent to worker threads (#11963)
• ref(feedback): Simplify feedback function params (#11957)

Bundle size 📦

Important Changes

• feat(node): Register ESM patching hooks in init for supported Node.js versions

This release includes adds support for ESM when Sentry.init() is called within a module imported via the --import
Node.js flag:

node --import ./your-file-with-sentry-init.mjs your-app.mjs

Note that the SDK only supports ESM for node versions 18.19.0 and above, and 20.6.0 above.

Other Changes

• deps(node): Bump @opentelemetry/core to 1.24.1 and @opentelemetry/instrumentation to 0.51.1 (#11941)
• feat(connect): Warn if connect is not instrumented (#11936)
• feat(express): Warn if express is not instrumented (#11930)
• feat(fastify): Warn if fastify is not instrumented (#11917)
• feat(hapi): Warn if hapi is not instrumented (#11937)
• feat(koa): Warn if koa is not instrumented (#11931)
• fix(browser): Continuously record CLS web vital (#11934)
• fix(feedback): Pick user from any scope (#11928)
• fix(node): Fix cron instrumentation and add tests (#11811)

Bundle size 📦

Important Changes

• fix(browser/v7): Continuously record CLS (#11935)

This release fixes a bug that caused the cumulative layout shift (CLS) web vital not to be reported in a majority of the
cases where it should have been reported. With this change, the CLS web vital should now always be reported for
pageloads with layout shift. If a pageload did not have layout shift, no CLS web vital should be reported.

Please note that upgrading the SDK to this version may cause data in your dashboards to drastically change.

Other Changes

• build(aws-lambda/v7): Turn off lambda layer publishing (#11875)
• feat(v7): Add tunnel support to multiplexed transport (#11851)
• fix(opentelemetry-node): support HTTP_REQUEST_METHOD attribute (#11929)
• fix(react/v7): Fix react router v4/v5 span names (#11940)

This release contains no changes and was done for technical purposes. This version is considered stable.

For the sake of completeness this changelog entry includes the changes from the previous release candidate:

We recommend to read the detailed migration guide in
the docs.

Important Changes

• feat(node): Support hapi v21 & fix E2E test (#11906)

We now support hapi v21 and added tests for it.

• feat(node): Warn if ESM mode is detected (#11914)

When running Sentry in ESM mode, we will now warn you that this is not supported as of now. We are working on ensuring
support with ESM builds.

Other Changes

• feat(feedback): Iterate on css for better scrolling & resizing when browser is small (#11893)
• fix(node): Ensure prisma integration creates valid DB spans (#11908)
• fix(node): Include loader hook files in package.json (#11911)

Bundle size 📦

This beta release contains various bugfixes and improvements for the v8 beta cycle.

• feat: Add tunnel support to multiplexed transport (#11806)
• feat: Export spanToBaggageHeader utility (#11881)
• feat(browser): Disable standalone http.client spans (#11879)
• feat(ember): Update ember dependencies (#11753)
• feat(fedback): Convert CDN bundles to use async feedback for lower bundle sizes (#11791)
• feat(feedback): Add captureFeedback method (#11428)
• feat(feedback): Have screenshot by default (#11839)
• feat(integrations): Add zod integration (#11144)
• feat(ioredis): Add integration for ioredis (#11856)
• feat(nextjs): Add transaction name to scope of server component (#11850)
• feat(nextjs): Be smarter in warning about old ways of init configuration (#11882)
• feat(nextjs): Set transaction names on scope for route handlers and generation functions (#11869)
• feat(node): Support Node 22 (#11871)
• fix(angular): Run tracing calls outside Angular (#11748)
• fix(feedback): Be consistent about whether screenshot should and can render (#11859)
• fix(nestjs): Ensure Nest.js interceptor works with non-http context (#11880)
• fix(node): Fix nest.js error handler (#11874)
• fix(react): Fix react router v4/v5 instrumentation (#11855)
• ref: Add geo location types (#11847)

Bundle size 📦

Important Changes

• feat(node): Support Node 22 (#11754)

This release adds support for Node 22! 🎉

It also adds prebuilt-binaries for Node 22 to @sentry/profiling-node.

Other Changes

• feat(feedback): [v7] New feedback button design (#11841)
• feat(replay/v7): Upgrade rrweb packages to 2.15.0 (#11752)
• fix(ember/v7): Ensure unnecessary spans are avoided (#11848)

This beta release contains various bugfixes and improvements for the v8 beta cycle.

Important Changes

• feat(svelte): Add Svelte 5 support (#11807)

We now officially support Svelte 5.

• feat(browser): Send standalone fetch and XHR spans if there's no active parent span (#11783)

Starting with this version, spans for outgoing fetch/xhr requests will be captured even if no pageload/navigation span
is ongoing. This means that you will be able to have a more complete trace, especially for web applications that make a
lot of HTTP requests on longer lived pages.

Other Changes

• feat(astro): Add transactionName to isolation scope for requests (#11786)
• feat(browser): Create standalone INP spans via startInactiveSpan (#11788)
• feat(core): Add trace envelope header to span envelope (#11699)
• feat(core): Add options to start standalone (segment) spans via start*Span APIs (#11696)
• feat(core): Set default scope for BaseClient methods (#11775)
• feat(core): Wrap cron withMonitor callback in withIsolationScope (#11797)
• feat(feedback): New feedback button design (#11641)
• feat(nextjs): Add transactionName to isolation scope for Next.js server side features (#11782)
• feat(nextjs): Mute webpack warnings about critical dependencies inside @opentelemetry/instrumentation (#11810)
• feat(node): Upgrade @prisma/instrumentation to 5.13.0 (#11779)
• feat(react): type error as unknown in ErrorBoundary (#11819)
• feat(remix): Add wrapHandleErrorWithSentry (#10370)
• feat(remix): Set formData as action span data. (#10836)
• feat(remix): Update scope transactionName for Remix server features (#11784)
• fix(angular): Call showReportDialog in root context (#11703)
• fix(core): Capture only failed console.assert calls (#11799)
• fix(ember): Ensure unnecessary spans are avoided (#11846)
• fix(feedback): Clarify the difference between createWidget and create Form in the feedback public api (#11838)
• fix(feedback): Fix feedback type (#11787)
• fix(feedback): Vendor preact into bundle (#11845)
• fix(remix): Rethrow loader, action and documentRequest errors (#11793)
• ref: Always return an immediately generated event ID from captureException(), captureMessage(), and
  captureEvent() (#11805)
• ref(core): Remove transaction name extraction from requestDataIntegration (#11513)
• ref(svelte): Use onlyIfParent for recording component update spans (#11809)

Bundle size 📦

Important Changes

• feat(browser): Add INP support for v8 (#11650)

INP web vital support was now forward-ported to version 8. Recording of INP data is enabled by default.

• feat(core): Increase default transport buffer size from 30 to 64 (#11764)

The default limit of queued events to be sent was increased from 30 to 64 events. You may observe a higher memory
footprint of the SDK. You can override this limit by setting the transportOptions.bufferSize option in
Sentry.init().

• feat(replay): Add "maxCanvasSize" option for replay canvases (#11617)

A maxCanvasSize option was added to the replayCanvasIntegration to disallow capturing of canvases larger than a
certain size. This value defaults to 1280 which will not capture canvases bigger than 1280x1280 pixels.

Other Changes

• deps: Downgrade @opentelemetry/instrumentation-http to 0.48.0 (#11745)
• deps(nextjs): Remove unnecessary and faulty @opentelemetry/api dependency from Next.js package (#11717)
• feat(aws): Add OTEL based integrations (#11548)
• feat(core): Ensure trace context only includes relevant data (#11713)
• feat(deps): Bump @opentelemetry/instrumentation-fastify from 0.33.0 to 0.35.0 (#11690)
• feat(deps): Bump @opentelemetry/instrumentation-graphql from 0.37.0 to 0.39.0 (#11692)
• feat(deps): Bump @opentelemetry/instrumentation-http from 0.48.0 to 0.50.0 (#11725)
• feat(deps): Bump @opentelemetry/instrumentation-mongoose from 0.35.0 to 0.37.0 (#11693)
• feat(deps): Bump @opentelemetry/instrumentation-mysql2 from 0.35.0 to 0.37.0 (#11726)
• feat(deps): Bump @opentelemetry/instrumentation-nestjs-core from 0.34.0 to 0.36.0 (#11727)
• feat(deps): Bump @opentelemetry/sdk-metrics from 1.21.0 to 1.23.0 (#11695)
• feat(deps): Bump @prisma/instrumentation from 5.9.0 to 5.12.1 (#11724)
• feat(feedback): Create async bundles and code to resolve helper integrations (#11621)
• feat(nextjs): Sample out low-quality spans on older Next.js versions (#11722)
• feat(opentelemetry): Support new http method attribute (#11756)
• feat(opentelemetry): Use rest args for addOpenTelemetryInstrumentation (#11721)
• feat(replay): Upgrade rrweb packages to 2.15.0 (#11736)
• fix(browser): Ensure lazyLoadIntegration works in NPM mode (#11673)
• fix(browser): Set custom sentry source correctly (#11735)
• fix(ember): Do not create rendering spans without transaction (#11749)
• fix(serverless): Check if cloud event callback is a function (#9044) (#11701)
• ref(nextjs): Remove unnecessary logic to filter symbolification/sentry spans (#11714)

Bundle size 📦

• fix(nextjs|sveltekit): Ensure we can pass browserTracingIntegration (#11765)

• fix(ember/v7): Do not create rendering spans without transaction (#11750)

Important Changes

• feat: Export pluggable integrations from SDK packages (#11723)

Instead of installing @sentry/integrations, you can now import the pluggable integrations directly from your SDK
package:

// Before
import * as Sentry fromv '@sentry/browser';
import { dedupeIntegration } from '@sentry/integrations';

Sentry.init({
  integrations: [dedupeIntegration()],
});

// After
import * as Sentry from '@sentry/browser';

Sentry.init({
  integrations: [Sentry.dedupeIntegration()],
});

Note that only the functional integrations (e.g. xxxIntegration()) are re-exported.

Other Changes

• feat(replay): Add "maxCanvasSize" option for replay canvases (#11732)
• fix(serverless): [v7] Check if cloud event callback is a function (#11734)

Bundle size 📦

Important Changes

• feat(opentelemetry): Add addOpenTelemetryInstrumentation (#11667)

A utility function addOpenTelemetryInstrumentation was added that allows for the registration of instrumentations that
conform to the OpenTelemetry JS API without having to specify @opentelemetry/instrumentation as a dependency.

• ref(core): Don't start transaction for trpc middleware (#11697)

Going forward, the Sentry trpcMiddleware will only create spans. Previously it used to always create a transaction.
This change was made to integrate more nicely with the HTTP instrumentation added in earlier versions to avoid creating
unnecessary transactions.

Other Changes

• feat(nextjs): Instrument outgoing http requests (#11685)
• feat(opentelemetry): Remove setupGlobalHub (#11668)
• fix: Missing ErrorEvent export are added to node, browser, bun, deno, vercel-edge sub-packages (#11649)
• fix(nextjs): Do not sample next spans if they have remote parent (#11680)
• fix(nextjs): Re-enable OTEL fetch instrumentation and disable Next.js fetch instrumentation (#11686)
• fix(node): Ensure DSC on envelope header uses root span (#11683)
• ref(browser): Streamline pageload span creation and scope handling (#11679)
• ref(core): Directly use endSession (#11669)

Bundle size 📦

• feat(core): Add server.address to browser http.client spans (#11663)
• fix: Ensure next & sveltekit correctly handle browserTracingIntegration (#11647)
• fix(browser): Don't assume window.document is available (#11598)

Bundle size 📦

Important Changes

• feat(browser): Update propagationContext on spanEnd to keep trace consistent

To ensure consistency throughout a route's duration, we update the scope's propagation context when the initial page
load or navigation span ends. This keeps span-specific attributes like the sampled decision and dynamic sampling context
on the scope, even after the transaction has ended.

• fix(browser): Don't assume window.document is available (#11602)

We won't assume window.dodument is available in the browser SDKs anymore. This should prevent errors in environments
where window.document is not available (such as web workers).

Other changes

• feat(core): Add server.address to browser http.client spans (#11634)
• feat(opentelemetry): Update OTEL packages & relax some version ranges (#11580)
• feat(deps): bump @opentelemetry/instrumentation-hapi from 0.34.0 to 0.36.0 (#11496)
• feat(deps): bump @opentelemetry/instrumentation-koa from 0.37.0 to 0.39.0 (#11495)
• feat(deps): bump @opentelemetry/instrumentation-pg from 0.38.0 to 0.40.0 (#11494)
• feat(nextjs): Skip OTEL root spans emitted by Next.js (#11623)
• feat(node): Collect Local Variables via a worker (#11586)
• fix(nextjs): Escape Next.js' OpenTelemetry instrumentation (#11625)
• fix(feedback): Fix timeout on feedback submission (#11619)
• fix(node): Allow use of NodeClient without calling init (#11585)
• fix(node): Ensure DSC is correctly set in envelope headers (#11628)

Bundle size 📦

This is the first beta release of Sentry JavaScript SDK v8. With this release, there are no more planned breaking
changes for the v8 cycle.

Read the in-depth migration guide to find out how to address any breaking changes in your code. All
deprecations from the v7 cycle, with the exception of getCurrentHub(), have been removed and can no longer be used in v8.

Version Support

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

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

• Chrome 63
• Edge 79
• Safari/iOS Safari 12
• Firefox 58
• Opera 50
• Samsung Internet 8.2

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

Package removal

The following packages will no longer be published

• @sentry/hub
• @sentry/tracing
• @sentry/integrations
• @sentry/serverless
• @sentry/replay

Initializing Server-side SDKs (Node, Bun, Next.js, SvelteKit, Astro, Remix):

Initializing the SDKs on the server-side has been simplified. See more details in our migration docs about
initializing the SDK in v8.

Performance Monitoring Changes

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

• Performance Monitoring API
• Performance Monitoring Integrations

Important Changes since v8.0.0-alpha.9

• feat(browser): Create spans as children of root span by default (#10986)

Because execution context isolation in browser environments does not work reliably, we deciced to keep a flat span
hierarchy by default in v8.

• feat(core): Deprecate addTracingExtensions (#11579)

Instead of calling Sentry.addTracingExtensions() if you want to use performance in a browser SDK without using
browserTracingIntegration(), you should now call Sentry.registerSpanErrorInstrumentation().

• feat(core): Implement suppressTracing (#11468)

You can use the new suppressTracing API to ensure a given callback will not generate any spans:

return Sentry.suppressTracing(() => {
  // Ensure this fetch call does not generate a span
  return fetch('/my-url');
});

• feat: Rename ESM loader hooks to import and loader (#11498)

We renamed the loader hooks for better clarity:

# For Node.js <= 18.18.2
node --loader=@sentry/node/loader app.js

# For Node.js >= 18.19.0
node --import=@sentry/node/import app.js

• feat(node): Do not exit process by default when other onUncaughtException handlers are registered in
  onUncaughtExceptionIntegration (#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 (#11447)
• feat(hapi): Update scope transactionName when handling request (#11448)
• feat(koa): Update scope transactionName when creating router span (#11476)
• feat(sveltekit): Update scope transactionName when handling server-side request (#11511)
• feat(nestjs): Update scope transaction name with parameterized route (#11510)

Removal/Refactoring of deprecated functionality

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

Other Changes

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

Bundle size 📦

• fix(nextjs): Fix tunnelRoute matching logic for hybrid cloud (#11577)

Bundle size 📦