Skip to content

fix(deps): update dependency @sentry/node to v8

Renovate requested to merge renovate/major-sentry-javascript-monorepo into v2

This MR contains the following updates:

Package Type Update Change
@sentry/node (source) dependencies major ^7.101.1 -> ^8.0.0

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

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

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

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 becomes conflicted, 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

Merge request reports