chore(deps): bump @sentry/node from 7.57.0 to 7.71.0

[dependabot]

Bumps @sentry/node from 7.57.0 to 7.71.0.

Release notes

Sourced from @​sentry/node's releases.

7.71.0

• feat(bun): Instrument Bun.serve (#9080)
• fix(core): Ensure global event processors are always applied to event (#9064)
• fix(core): Run client eventProcessors before global ones (#9032)
• fix(nextjs): Use webpack module paths to attempt to resolve internal request async storage module (#9100)
• fix(react): Add actual error name to boundary error name (#9065)
• fix(react): Compare location against basename-prefixed route. (#9076)
• ref(browser): Refactor browser integrations to use processEvent (#9022)

Work in this release contributed by @​jorrit. Thank you for your contribution!

Bundle size 📦

Path	Size
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	75.58 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped)	31.46 KB
@​sentry/browser - Webpack (gzipped)	22.06 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	70.27 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.57 KB
@​sentry/browser - ES6 CDN Bundle (gzipped)	20.64 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	222.17 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	86.57 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed)	61.42 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	31.43 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	75.6 KB
@​sentry/react - Webpack (gzipped)	22.09 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	93.48 KB
@​sentry/nextjs Client - Webpack (gzipped)	51.04 KB

7.70.0

Important Changes

• feat: Add Bun SDK (#9029)

This release contains the beta version of @sentry/bun, our SDK for the Bun 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.

Note that as of now the Bun runtime does not support global error handlers. This is being actively worked on, see the tracking issue in Bun's GitHub repo.

• feat(remix): Add Remix 2.x release support. (#8940)

The Sentry Remix SDK now officially supports Remix v2! See our Remix docs for more details.

Other Changes

• chore(node): Upgrade cookie to ^0.5.0 (#9013)
• feat(core): Introduce processEvent hook on Integration (#9017)
• feat(node): Improve non-error messages (#9026)
• feat(vercel-edge): Add Vercel Edge Runtime package (#9041)
• fix(remix): Use React.ComponentType instead of React.FC as withSentry's generic type. (#9043)

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

7.71.0

• feat(bun): Instrument Bun.serve (#9080)
• fix(core): Ensure global event processors are always applied to event (#9064)
• fix(core): Run client eventProcessors before global ones (#9032)
• fix(nextjs): Use webpack module paths to attempt to resolve internal request async storage module (#9100)
• fix(react): Add actual error name to boundary error name (#9065)
• fix(react): Compare location against basename-prefixed route. (#9076)
• ref(browser): Refactor browser integrations to use processEvent (#9022)

Work in this release contributed by @​jorrit. Thank you for your contribution!

7.70.0

Important Changes

• feat: Add Bun SDK (#9029)

This release contains the beta version of @sentry/bun, our SDK for the Bun 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.

Note that as of now the Bun runtime does not support global error handlers. This is being actively worked on, see the tracking issue in Bun's GitHub repo.

• feat(remix): Add Remix 2.x release support. (#8940)

The Sentry Remix SDK now officially supports Remix v2! See our Remix docs for more details.

Other Changes

• chore(node): Upgrade cookie to ^0.5.0 (#9013)
• feat(core): Introduce processEvent hook on Integration (#9017)
• feat(node): Improve non-error messages (#9026)
• feat(vercel-edge): Add Vercel Edge Runtime package (#9041)
• fix(remix): Use React.ComponentType instead of React.FC as withSentry's generic type. (#9043)
• fix(replay): Ensure replay events go through preprocessEvent hook (#9034)
• fix(replay): Fix typo in Replay types (#9028)
• fix(sveltekit): Adjust handleErrorWithSentry type (#9054)
• fix(utils): Try-catch monkeypatching to handle frozen objects/functions (#9031)

Work in this release contributed by @​Dima-Dim, @​krist7599555 and @​lifeiscontent. Thank you for your contributions!

Special thanks for @​isaacharrisholt for helping us implement a Vercel Edge Runtime SDK which we use under the hood for our Next.js SDK.

7.69.0

Important Changes

• New Performance APIs
  • feat: Update span performance API names (#8971)
  • feat(core): Introduce startSpanManual (#8913)

... (truncated)

Commits

• e3a51df release: 7.71.0
• 3ee7e00 Merge pull request #9103 from getsentry/prepare-release/7.71.0
• 90b0c1f meta(changelog): Update changelog for 7.71.0
• 622186c fix(nextjs): Use webpack module paths to attempt to resolve internal request ...
• 705be9b ref(opentelemetry-node): Extract maybeCaptureExceptionForTimedEvent (#9099)
• 0532541 chore: Publish @​sentry/vercel-edge to release registry (#9074)
• d94e72a ref(node-experimental): Reorder files into opentelemetry folder (#9084)
• 9dc0f12 build(deps): bump graphql from 16.3.0 to 16.8.1
• 1f8de57 fix(react): Add actual error name to boundary error name (#9065)
• 8001498 feat(bun): Instrument Bun.serve (#9080)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[adaptly-bot]

⚠️  @sentry/[email protected]

 Breaking changes

1: feat(replay): Ensure min/max duration when flushing (#8596)

The package will no longer send replays that are less than 5 seconds long. You can configure the minimum replay duration, but it is capped at 15 seconds. If your application relies on short replays, you may need to adjust your code to handle this change.

[adaptly-bot]

⚠️  @sentry/[email protected]

 Breaking changes

1: build: Remove build-specific polyfills (#8809)

The build-specific polyfills have been removed. If your project relies on these polyfills, you may need to add them manually.

2: ref(sveltekit): Remove custom client fetch instrumentation and use default instrumentation (#8802)

The custom client fetch instrumentation in SvelteKit has been removed and replaced with the default instrumentation. If you were using the custom client fetch instrumentation, you will need to update your code to use the default instrumentation.

3: ref(tracing-internal): Deprecate tracePropagationTargets in BrowserTracing (#8874)

tracePropagationTargets in BrowserTracing has been deprecated. If you are using this feature, you should plan to update your code to avoid using it.

[adaptly-bot]

⚠️  @sentry/[email protected]

 Breaking changes

1: feat: Mark errors caught by the SDK as unhandled

All errors caught automatically from the SDKs will now be marked as unhandled. This change might lead to a decrease in reported crash-free sessions and consequently in your release health score. If you manually capture errors (e.g. by calling Sentry.captureException), your errors will continue to be reported as handled.

2: ref(browser): Deprecate top-level wrap function

The top-level wrap function has been deprecated. This might break existing code that relies on this function.

[dependabot]

Superseded by #103.