fix(deps): update sentry-javascript monorepo - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/node (source)	8.49.0 -> 8.55.0
@sentry/tracing (source)	7.114.0 -> 7.120.3

---

Release Notes

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

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 '@​solidjs/start/config';
import { withSentry } from '@​sentry/solidstart';

export default defineConfig(
  withSentry(
    {
      /* Your SolidStart config options... */
    },
    {
      // Options for setting up source maps
      org: process.env.SENTRY_ORG,
      project: process.env.SENTRY_PROJECT,
      authToken: process.env.SENTRY_AUTH_TOKEN,
    },
  ),
);

With the withSentry wrapper, the Sentry server config should not be added to the public directory anymore.
Add the Sentry server config in src/instrument.server.ts. Then, the server config will be placed inside the server build output as instrument.server.mjs.

Now, there are two options to set up the SDK:

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 '@​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)

---

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 PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a2eb1f5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR