Bump @sentry/browser from 7.71.0 to 7.72.0

[dependabot]

Bumps @sentry/browser from 7.71.0 to 7.72.0.

Release notes

Sourced from @​sentry/browser's releases.

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.

Example (ESM):

import * as Sentry from "@sentry/node";
Sentry.init({
dsn: "PUBLIC_DSN",
tracesSampleRate: 1.0,
});
await Sentry.enableANRDetection({ captureStackTrace: true });
// Function that runs your app
runApp();

Example (CJS):

const Sentry = require("@sentry/node");
Sentry.init({
dsn: "PUBLIC_DSN",
tracesSampleRate: 1.0,
});
Sentry.enableANRDetection({ captureStackTrace: true }).then(() => {
// Function that runs your app
runApp();
});

Other Changes

• fix(nextjs): Filter RequestAsyncStorage locations by locations that webpack will resolve (#9114)
• fix(replay): Ensure replay_id is not captured when session is expired (#9109)

Bundle size 📦

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

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.

Example (ESM):

import * as Sentry from "@sentry/node";
Sentry.init({
dsn: "PUBLIC_DSN",
tracesSampleRate: 1.0,
});
await Sentry.enableANRDetection({ captureStackTrace: true });
// Function that runs your app
runApp();

Example (CJS):

const Sentry = require("@sentry/node");
Sentry.init({
dsn: "PUBLIC_DSN",
tracesSampleRate: 1.0,
});
Sentry.enableANRDetection({ captureStackTrace: true }).then(() => {
// Function that runs your app
runApp();
});

Other Changes

• fix(nextjs): Filter RequestAsyncStorage locations by locations that webpack will resolve (#9114)
• fix(replay): Ensure replay_id is not captured when session is expired (#9109)

Commits

• e7bd97b release: 7.72.0
• f736381 Merge pull request #9118 from getsentry/prepare-release/7.72.0
• 779cd26 meta(changelog): Update changelog for 7.72.0
• a57b66d fix(nextjs): Filter RequestAsyncStorage locations by locations that webpack...
• 618e992 fix(replay): Ensure replay_id is not captured when session is expired (#9109)
• c326e15 ref(node-experimental): Add resource information (#9088)
• 5a8d4aa feat(node): App Not Responding with stack traces (#9079)
• 50a36bf Merge pull request #9105 from getsentry/master
• 7614bb9 Merge branch 'release/7.71.0'
• a7cce7b fix(node): Remove dom lib types (#9090)
• See full diff 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)

[zspencer]

@dependabot squash and merge