fix(deps): update dependency @sentry/nuxt to v9.16.0 #2423

2025-05-07T15:03:16Z

group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 commented

2025-05-07 15:03:16 +00:00

(Migrated from gitlab.com)

This MR contains the following updates:

Package	Type	Update	Change
@sentry/nuxt (source)	dependencies	minor	`9.15.0` -> `9.16.0`

Release Notes

getsentry/sentry-javascript (@sentry/nuxt)

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

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.

This MR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@sentry/nuxt](https://github.com/getsentry/sentry-javascript/tree/master/packages/nuxt) ([source](https://github.com/getsentry/sentry-javascript)) | dependencies | minor | [`9.15.0` -> `9.16.0`](https://renovatebot.com/diffs/npm/@sentry%2fnuxt/9.15.0/9.16.0) | --- ### Release Notes <details> <summary>getsentry/sentry-javascript (@sentry/nuxt)</summary> ### [`v9.16.0`](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#9160) [Compare Source](https://github.com/getsentry/sentry-javascript/compare/9.15.0...9.16.0) ##### Important changes - **feat: Create a Vite plugin that injects sentryConfig into the global config ([#16197](https://github.com/getsentry/sentry-javascript/pull/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](https://github.com/getsentry/sentry-javascript/pull/16037))** This MR implements consistent sampling across traces as outlined in ([#15754](https://github.com/getsentry/sentry-javascript/pull/15754)) - **feat(cloudflare): Add support for durable objects ([#16180](https://github.com/getsentry/sentry-javascript/pull/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](https://github.com/getsentry/sentry-javascript/pull/16073))** [Prisma integration](https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/integrations/prisma/) is enabled by default, it should work for both ESM and CJS. - **feat(react-router): Add client-side router instrumentation ([#16185](https://github.com/getsentry/sentry-javascript/pull/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](https://github.com/getsentry/sentry-javascript/pull/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 diagnostics*channel 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: ```ts 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](https://github.com/getsentry/sentry-javascript/pull/16165)) - feat(vercel-edge): Add logs export ([#16166](https://github.com/getsentry/sentry-javascript/pull/16166)) - feat(cloudflare): Read `SENTRY_RELEASE` from `env` ([#16201](https://github.com/getsentry/sentry-javascript/pull/16201)) - feat(node): Drop `http.server` spans with 404 status by default ([#16205](https://github.com/getsentry/sentry-javascript/pull/16205)) - fix(browser): Respect manually set sentry tracing headers in XHR requests ([#16184](https://github.com/getsentry/sentry-javascript/pull/16184)) - fix(core): Respect manually set sentry tracing headers in fetch calls ([#16183](https://github.com/getsentry/sentry-javascript/pull/16183)) - fix(feedback): Prevent `removeFromDom()` from throwing ([#16030](https://github.com/getsentry/sentry-javascript/pull/16030)) - fix(node): Use class constructor in docstring for winston transport ([#16167](https://github.com/getsentry/sentry-javascript/pull/16167)) - fix(node): Fix vercel flushing logic & add test for it ([#16208](https://github.com/getsentry/sentry-javascript/pull/16208)) - fix(node): Fix 404 route handling in express 5 ([#16211](https://github.com/getsentry/sentry-javascript/pull/16211)) - fix(logs): Ensure logs can be flushed correctly ([#16216](https://github.com/getsentry/sentry-javascript/pull/16216)) - ref(core): Switch to standardized log envelope ([#16133](https://github.com/getsentry/sentry-javascript/pull/16133)) </details> --- ### 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](https://github.com/renovatebot/renovate).

group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 commented

2025-05-07 15:03:20 +00:00

(Migrated from gitlab.com)

mentioned in issue #49

argoyle (Migrated from gitlab.com) scheduled this pull request to auto merge when all checks succeed 2025-05-07 15:06:07 +00:00

argoyle (Migrated from gitlab.com) merged commit into main

2025-05-07 15:06:22 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dancefinder/dancefinder-app#2423