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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/node (source)	8.51.0 -> 8.52.0

---

Release Notes

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

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!

Bundle size 📦

Path	Size
@​sentry/browser	23.32 KB
@​sentry/browser - with treeshaking flags	23.2 KB
@​sentry/browser (incl. Tracing)	35.88 KB
@​sentry/browser (incl. Tracing, Replay)	73.23 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.7 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	77.54 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	89.47 KB
@​sentry/browser (incl. Feedback)	39.53 KB
@​sentry/browser (incl. sendFeedback)	27.94 KB
@​sentry/browser (incl. FeedbackAsync)	32.73 KB
@​sentry/react	26 KB
@​sentry/react (incl. Tracing)	38.71 KB
@​sentry/vue	27.6 KB
@​sentry/vue (incl. Tracing)	37.74 KB
@​sentry/svelte	23.49 KB
CDN Bundle	24.52 KB
CDN Bundle (incl. Tracing)	37.59 KB
CDN Bundle (incl. Tracing, Replay)	72.87 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	78.24 KB
CDN Bundle - uncompressed	72.01 KB
CDN Bundle (incl. Tracing) - uncompressed	111.51 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	225.76 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	238.86 KB
@​sentry/nextjs (client)	38.96 KB
@​sentry/sveltekit (client)	36.39 KB
@​sentry/node	162.87 KB
@​sentry/node - without tracing	99.18 KB
@​sentry/aws-serverless	126.69 KB

---

Configuration

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

🚦 Automerge: Enabled.

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

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

---

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

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