chore(deps): bump @sentry/browser from 8.18.0 to 8.36.0

dependabot[bot] commented 2 weeks ago

Bumps @sentry/browser from 8.18.0 to 8.36.0.

Release notes

Sourced from @sentry/browser's releases.

8.36.0

Important Changes

feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)

With this release, the Sentry Next.js, and Cloudflare SDKs will now capture performance data based on OpenTelemetry. Some exceptions apply in cases where Next.js captures inaccurate data itself.

NOTE: You may experience minor differences in transaction names in Sentry. Most importantly transactions for serverside pages router invocations will now be named GET /[param]/my/route instead of /[param]/my/route. This means that those transactions are now better aligned with the OpenTelemetry semantic conventions.

Other Changes

deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)

feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)

feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)

feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)

feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)

feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)

feat(nextjs): Add method and url to route handler request data (#14084)

feat(node): Add breadcrumbs for child_process and worker_thread (#13896)

fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)

fix(nextjs): Await flush in api handlers (#14023)

fix(nextjs): Don't leak webpack types into exports (#14116)

fix(nextjs): Fix matching logic for file convention type for root level components (#14038)

fix(nextjs): Respect directives in value injection loader (#14083)

fix(nuxt): Only wrap .mjs entry files in rollup (#14060)

fix(nuxt): Re-export all exported bindings (#14086)

fix(nuxt): Server-side setup in readme (#14049)

fix(profiling-node): Always warn when running on incompatible major version of Node.js (#14043)

fix(replay): Fix onError callback (#14002)

perf(otel): Only calculate current timestamp once (#14094)

test(browser-integration): Add sentry DSN route handler by default (#14095)

Bundle size 📦

Path Size

@sentry/browser 22.73 KB

@sentry/browser - with treeshaking flags 21.52 KB

@sentry/browser (incl. Tracing) 35.11 KB

@sentry/browser (incl. Tracing, Replay) 71.82 KB

@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.26 KB

@sentry/browser (incl. Tracing, Replay with Canvas) 76.13 KB

@sentry/browser (incl. Tracing, Replay, Feedback) 88.94 KB

@sentry/browser (incl. Tracing, Replay, Feedback, metrics) 90.77 KB

@sentry/browser (incl. metrics) 26.98 KB

@sentry/browser (incl. Feedback) 39.87 KB

@sentry/browser (incl. sendFeedback) 27.37 KB

Path	Size
`@sentry/browser`	22.73 KB
`@sentry/browser` - with treeshaking flags	21.52 KB
`@sentry/browser` (incl. Tracing)	35.11 KB
`@sentry/browser` (incl. Tracing, Replay)	71.82 KB
`@sentry/browser` (incl. Tracing, Replay) - with treeshaking flags	62.26 KB
`@sentry/browser` (incl. Tracing, Replay with Canvas)	76.13 KB
`@sentry/browser` (incl. Tracing, Replay, Feedback)	88.94 KB
`@sentry/browser` (incl. Tracing, Replay, Feedback, metrics)	90.77 KB
`@sentry/browser` (incl. metrics)	26.98 KB
`@sentry/browser` (incl. Feedback)	39.87 KB
`@sentry/browser` (incl. sendFeedback)	27.37 KB

... (truncated)

Changelog

Sourced from @sentry/browser's changelog.

8.36.0

Important Changes

feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)

With this release, the Sentry Next.js, and Cloudflare SDKs will now capture performance data based on OpenTelemetry. Some exceptions apply in cases where Next.js captures inaccurate data itself.

NOTE: You may experience minor differences in transaction names in Sentry. Most importantly transactions for serverside pages router invocations will now be named GET /[param]/my/route instead of /[param]/my/route. This means that those transactions are now better aligned with the OpenTelemetry semantic conventions.

Other Changes

deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)

feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)

feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)

feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)

feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)

feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)

feat(nextjs): Add method and url to route handler request data (#14084)

feat(node): Add breadcrumbs for child_process and worker_thread (#13896)

fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)

fix(nextjs): Await flush in api handlers (#14023)

fix(nextjs): Don't leak webpack types into exports (#14116)

fix(nextjs): Fix matching logic for file convention type for root level components (#14038)

fix(nextjs): Respect directives in value injection loader (#14083)

fix(nuxt): Only wrap .mjs entry files in rollup (#14060)

fix(nuxt): Re-export all exported bindings (#14086)

fix(nuxt): Server-side setup in readme (#14049)

fix(profiling-node): Always warn when running on incompatible major version of Node.js (#14043)

fix(replay): Fix onError callback (#14002)

perf(otel): Only calculate current timestamp once (#14094)

test(browser-integration): Add sentry DSN route handler by default (#14095)

8.35.0

Beta release of the official Nuxt Sentry SDK

This release marks the beta release of the @sentry/nuxt Sentry SDK. For details on how to use it, check out the Sentry Nuxt SDK README. Please reach out on GitHub if you have any feedback or concerns.

feat(nuxt): Make dynamic import() wrapping default (#13958) (BREAKING)

feat(nuxt): Add Rollup plugin to wrap server entry with import() (#13945)

**It is no longer required to add a Node --import flag. Please update your start command to avoid initializing Sentry

... (truncated)

Commits

13e6c8e release: 8.36.0
a566681 Merge pull request #14136 from getsentry/prepare-release/8.36.0
09c8577 meta(changelog): Update changelog for 8.36.0
b6dbde8 Merge pull request #14135 from getsentry/master
472c228 ref(nuxt): Revert Sentry Pinia plugin (#14134)
a9cedf9 Merge pull request #14120 from getsentry/prepare-release/8.36.0
c98377b fix(aws-serverless): Remove possible prototype pollution source (#14110)
a091bdd feat(replay): Expose recordingMode in public API (#14085)
8d9322c meta(changelog): Update changelog for 8.36.0
06ef628 feat(nextjs): Add method and url to route handler request data (#14084)
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 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/SocialGouv/domifa/network/alerts).