build(deps): bump @sentry/browser from 6.4.0 to 7.47.0
Bumps @sentry/browser from 6.4.0 to 7.47.0.
Release notes
Sourced from @sentry/browser's releases.
7.47.0
Important Changes
- feat(browser): Add captureUserFeedback (#7729)
This release adds a new API,
Sentry.captureUserFeedback, to browser-side SDKs that allows you to send user feedback to Sentry without loading and opening Sentry's user feedback dialog. This allows you to obtain user feedback however and whenever you want to and simply send it to Sentry using the SDK.For instance, you can collect feedback, whenever convenient as shown in this example:
const eventId = Sentry.captureMessage('User Feedback'); const user = Sentry.getCurrentHub().getScope().getUser(); const userFeedback = { event_id: eventId; email: user.email name: user.username comments: 'I really like your App, thanks!' } Sentry.captureUserFeedback(userFeedback);Note that feedback needs to be coupled to an event but as in the example above, you can just use
Sentry.captureMessageto generate one.You could also collect feedback in a custom way if an error happens and use the SDK to send it along:
Sentry.init({ dsn: '__DSN__', beforeSend: event => { const userFeedback = collectYourUserFeedback(); const feedback = { ...userFeedback, event_id: event.event_id. } Sentry.captureUserFeedback(feedback); return event; } })
- feat(tracing): Deprecate
@sentry/tracingexports (#7611)With this release, we officially deprecate all exports from the
@sentry/tracingpackage, in favour of using them directly from the main SDK package. The@sentry/tracingpackage will be removed in a future major release.Please take a look at the Migration docs for more details.
Additional Features and Fixes
... (truncated)
Changelog
Sourced from @sentry/browser's changelog.
7.47.0
Important Changes
- feat(browser): Add captureUserFeedback (#7729)
This release adds a new API,
Sentry.captureUserFeedback, to browser-side SDKs that allows you to send user feedback to Sentry without loading and opening Sentry's user feedback dialog. This allows you to obtain user feedback however and whenever you want to and simply send it to Sentry using the SDK.For instance, you can collect feedback, whenever convenient as shown in this example:
const eventId = Sentry.captureMessage('User Feedback'); const user = Sentry.getCurrentHub().getScope().getUser(); const userFeedback = { event_id: eventId; email: user.email name: user.username comments: 'I really like your App, thanks!' } Sentry.captureUserFeedback(userFeedback);Note that feedback needs to be coupled to an event but as in the example above, you can just use
Sentry.captureMessageto generate one.You could also collect feedback in a custom way if an error happens and use the SDK to send it along:
Sentry.init({ dsn: '__DSN__', beforeSend: event => { const userFeedback = collectYourUserFeedback(); const feedback = { ...userFeedback, event_id: event.event_id. } Sentry.captureUserFeedback(feedback); return event; } })
- feat(tracing): Deprecate
@sentry/tracingexports (#7611)With this release, we officially deprecate all exports from the
@sentry/tracingpackage, in favour of using them directly from the main SDK package. The@sentry/tracingpackage will be removed in a future major release.Please take a look at the Migration docs for more details.
Additional Features and Fixes
... (truncated)
Commits
ad7b876release: 7.47.0f4861f8Merge pull request #7758 from getsentry/prepare-release/7.47.056268f9meta: Update changelog for 7.47.041ba98afix(node): DisableLocalVariablesintegration on Node < v18 (#7748)1d7f18ffix(replay): Ensure circular references are handled (#7752)c90a60ffeat(browser): AddcaptureUserFeedback(#7729)367f779fix(react): Only show report dialog if event was sent to Sentry (#7754)2531853fix(angular): Only open report dialog if error was sent (#7750)105dcf1feat(sveltekit): Add partial instrumentation for client-side fetch (#7626)8ccb82dfix(node): Redact URL authority only in breadcrumbs and spans (#7740)- 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)