ref(core)!: Remove supportsDOMError, supportsHistory, supportsReportingObserver exports - #23718
Conversation
d0454a2 to
07f89b5
Compare
supportsDOMError, supportsHistory, supportsReportingObserver exportssupportsDOMError, supportsHistory, supportsReportingObserver exports
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 07f89b5. Configure here.
|
|
||
| export { getComponentName, getLocationHref } from './utils/browser'; | ||
| export { supportsDOMError, supportsHistory, supportsNativeFetch, supportsReportingObserver } from './utils/supports'; | ||
| export { supportsNativeFetch } from './utils/supports'; |
There was a problem hiding this comment.
Public support helpers removed without deprecation
Medium Severity
supportsDOMError, supportsHistory, and supportsReportingObserver were dropped from the public @sentry/core and @sentry/core/browser entry points with no deprecation window. This is flagged because the review rules call out public API removals and missing deprecation notices. Downstream imports of these helpers will fail in a minor release. Nearby unused helpers such as supportsFetch and supportsReferrerPolicy remain exported and marked deprecated instead.
Additional Locations (1)
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit 07f89b5. Configure here.
size-limit report 📦
|
07f89b5 to
365491f
Compare
…ortingObserver` exports
365491f to
30a2c1f
Compare


These are no longer used in core, and can just move directly to browser/browser-utils, or be removed (
supportsDOMErroris not used anywhere).