[Snyk] Upgrade @sentry/utils from 7.60.1 to 7.73.0 #138
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @sentry/utils from 7.60.1 to 7.73.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: @sentry/utils
Important Changes
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 maskaria-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
Other Changes
captureAllExceptions
by default (#9102)tunnel
is considered forisSentryUrl
checks (#9130)RequestAsyncStorage
fallback path (#9126)load
functions (#9071)InboundFilters
integration to useprocessEvent
(#9020)processEvent
(#9019)Work in this release contributed by @ vlad-zhukov. Thank you for your contribution!
Bundle size 📦
Important Changes
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.Example (ESM):
Sentry.init({
dsn: "PUBLIC_DSN",
tracesSampleRate: 1.0,
});
await Sentry.enableANRDetection({ captureStackTrace: true });
// Function that runs your app
runApp();
Example (CJS):
Sentry.init({
dsn: "PUBLIC_DSN",
tracesSampleRate: 1.0,
});
Sentry.enableANRDetection({ captureStackTrace: true }).then(() => {
// Function that runs your app
runApp();
});
Other Changes
RequestAsyncStorage
locations by locations that webpack will resolve (#9114)replay_id
is not captured when session is expired (#9109)Bundle size 📦
basename
-prefixed route. (#9076)processEvent
(#9022)Work in this release contributed by @ jorrit. Thank you for your contribution!
Bundle size 📦
Read more
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs