search

scalacenter / scastie

An interactive playground for Scala
https://scastie.scala-lang.org
Apache License 2.0
432 stars 104 forks source link

Bump @sentry/browser from 7.70.0 to 7.73.0 #965

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @sentry/browser from 7.70.0 to 7.73.0.

Release notes

Sourced from @​sentry/browser's releases.

7.73.0

Important Changes

  • feat(replay): Upgrade to rrweb2

This is fully backwards compatible with prior versions of the Replay SDK. The only breaking change that we will making is to not be masking aria-label by default. The reason for this change is to align with our core SDK which also does not mask aria-label. This change also enables better support of searching by clicks.

Another change that needs to be highlighted is the 13% bundle size increase. This bundle size increase is necessary to bring improved recording performance and improved replay fidelity, especially in regards to web components and iframes. We will be investigating the reduction of the bundle size in this PR.

Here are benchmarks comparing the version 1 of rrweb to version 2

metric v1 v2
lcp 1486.06 ms 1529.11 ms
cls 0.40 ms 0.40 ms
fid 1.53 ms 1.50 ms
tbt 3207.22 ms 3036.80 ms
memoryAvg 131.83 MB 124.84 MB
memoryMax 324.8 MB 339.03 MB
netTx 282.67 KB 272.51 KB
netRx 8.02 MB 8.07 MB

Other Changes

  • feat: Always assemble Envelopes (#9101)
  • feat(node): Rate limit local variables for caught exceptions and enable captureAllExceptions by default (#9102)
  • fix(core): Ensure tunnel is considered for isSentryUrl checks (#9130)
  • fix(nextjs): Fix RequestAsyncStorage fallback path (#9126)
  • fix(node-otel): Suppress tracing for generated sentry spans (#9142)
  • fix(node): fill in span data from http request options object (#9112)
  • fix(node): Fixes and improvements to ANR detection (#9128)
  • fix(sveltekit): Avoid data invalidation in wrapped client-side load functions (#9071)
  • ref(core): Refactor InboundFilters integration to use processEvent (#9020)
  • ref(wasm): Refactor Wasm integration to use processEvent (#9019)

Work in this release contributed by @​vlad-zhukov. Thank you for your contribution!

Bundle size 📦

Path Size
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 84.26 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped) 31.42 KB
@​sentry/browser - Webpack (gzipped) 22 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 78.69 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 28.52 KB
@​sentry/browser - ES6 CDN Bundle (gzipped) 20.59 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 254.14 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 86.42 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed) 61.23 KB

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

7.73.0

Important Changes

  • feat(replay): Upgrade to rrweb2

This is fully backwards compatible with prior versions of the Replay SDK. The only breaking change that we will making is to not be masking aria-label by default. The reason for this change is to align with our core SDK which also does not mask aria-label. This change also enables better support of searching by clicks.

Another change that needs to be highlighted is the 13% bundle size increase. This bundle size increase is necessary to bring improved recording performance and improved replay fidelity, especially in regards to web components and iframes. We will be investigating the reduction of the bundle size in this PR.

Here are benchmarks comparing the version 1 of rrweb to version 2

metric v1 v2
lcp 1486.06 ms 1529.11 ms
cls 0.40 ms 0.40 ms
fid 1.53 ms 1.50 ms
tbt 3207.22 ms 3036.80 ms
memoryAvg 131.83 MB 124.84 MB
memoryMax 324.8 MB 339.03 MB
netTx 282.67 KB 272.51 KB
netRx 8.02 MB 8.07 MB

Other Changes

  • feat: Always assemble Envelopes (#9101)
  • feat(node): Rate limit local variables for caught exceptions and enable captureAllExceptions by default (#9102)
  • fix(core): Ensure tunnel is considered for isSentryUrl checks (#9130)
  • fix(nextjs): Fix RequestAsyncStorage fallback path (#9126)
  • fix(node-otel): Suppress tracing for generated sentry spans (#9142)
  • fix(node): fill in span data from http request options object (#9112)
  • fix(node): Fixes and improvements to ANR detection (#9128)
  • fix(sveltekit): Avoid data invalidation in wrapped client-side load functions (#9071)
  • ref(core): Refactor InboundFilters integration to use processEvent (#9020)
  • ref(wasm): Refactor Wasm integration to use processEvent (#9019)

Work in this release contributed by @​vlad-zhukov. Thank you for your contribution!

7.72.0

Important Changes

  • feat(node): App Not Responding with stack traces (#9079)

This release introduces support for Application Not Responding (ANR) errors for Node.js applications. These errors are triggered when the Node.js main thread event loop of an application is blocked for more than five seconds. The Node SDK reports ANR errors as Sentry events and can optionally attach a stacktrace of the blocking code to the ANR event.

To enable ANR detection, import and use the enableANRDetection function from the @sentry/node package before you run the rest of your application code. Any event loop blocking before calling enableANRDetection will not be detected by the SDK.

... (truncated)

Commits
  • 6c1f2f1 release: 7.73.0
  • 6ad3d7e Merge pull request #9144 from getsentry/prepare-release/7.73.0
  • 53d283e meta(changelog): Update changelog for 7.73.0
  • c356073 fix(sveltekit): Avoid data invalidation in wrapped client-side load functio...
  • d67ab0b ci(deps): bump actions/checkout from 3 to 4 (#9148)
  • 9ae1ed2 build(replay): Cleanup unused config (#9140)
  • 1bcca84 fix(node-otel): Suppress tracing for generated sentry spans (#9142)
  • f112204 ref(core): Split transaction finish into underlying _finishTransaction (#...
  • f22bb15 fix(node): Fixes and improvements to ANR detection (#9128)
  • aa41f97 feat(node): Rate limit local variables for caught exceptions and enable `capt...
  • Additional commits viewable in compare view


Dependabot compatibility score

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)
dependabot[bot] commented 1 year ago

Superseded by #966.