chore(deps): bump @sentry/browser from 5.23.0 to 7.0.0

[dependabot[bot]]

Bumps @sentry/browser from 5.23.0 to 7.0.0.

Release notes

Sourced from @​sentry/browser's releases.

7.0.0

Version 7 of the Sentry JavaScript SDK brings a variety of features and fixes including bundle size and performance improvements, brand new integrations, support for the attachments API, and key bug fixes.

This release does not change or remove any top level public API methods (captureException, captureMessage), and only requires changes to certain configuration options or custom clients/integrations/transports.

Note: The v7 version of the JavaScript SDK requires a self-hosted version of Sentry 20.6.0 or higher. If you are using a version of self-hosted Sentry (aka onpremise) older than 20.6.0 then you will need to upgrade.

For detailed overview of all the changes, please see our v7 migration guide.

Breaking Changes

If you are a regular consumer of the Sentry JavaScript SDK you only need to focus on the general items. The internal breaking changes are aimed at libraries that build on top of and extend the JavaScript SDK (like @sentry/electron or @sentry/react-native).

General

• Updated CommonJS distributions to use ES6 by default. If you need to support Internet Explorer 11 or old Node.js versions, we recommend using a preprocessing tool like Babel to convert Sentry packages to ES5. (#5005)
• Default bundle.min.js to ES6 instead of ES5. ES5 bundles are still available at bundle.es5.min.js. (#4958)
• Updated build system to use TypeScript 3.8.3 (#4895)
• Deprecated Severity enum for bundle size reasons. Please use string literals instead. (#4926)
• Removed critical Severity level. (#5032)
• whitelistUrls and blacklistUrls have been renamed to allowUrls and denyUrls in the Sentry.init() options. (#4850)
• BaseClient and it's child classes now require transport, stackParser, and integrations to be explicitly passed in. This was done to improve tree-shakability. (#4927)
• Updated package distribution structure and stopped distributing CDN bundles through @sentry/* npm packages. See details in our migration docs. (#4900) (#4901)
• Simplified Transport API. This means custom transports will have to be adjusted accordingly.
• Updated how Node Transport Options are passed down.
• Start propogating baggage HTTP header alongside sentry-trace header to propogate additional tracing related information. (#5133)
• Renamed registerRequestInstrumentation export to instrumentOutgoingRequests in @sentry/tracing. (#4859)
• Renamed UserAgent integration to HttpContext. (#5027)
• Replaced BrowserTracing integration's maxTransactionDuration option with finalTimeout option in the @sentry/tracing package and reset idleTimeout based on activities count. This should improve accuracy of web-vitals like LCP by 20-30%. (#5044)
• Updated @sentry/angular to be compiled by the angular compiler. (#4641)
• Made tracing package treeshakable (#5166)
• Removed support for Node v6. (#4851)
• Removed @sentry/minimal package in favour of using @sentry/hub. (#4971)
• Removed support for Opera browser pre v15 (#4923)
• Removed ignoreSentryErrors option from AWS lambda SDK. Errors originating from the SDK will now always be caught internally. (#4994)
• Removed Integrations.BrowserTracing export from @sentry/nextjs. Please import BrowserTracing from @sentry/nextjs directly.
• Removed static id property from BrowserTracing integration.
• Removed SDK_NAME export from @sentry/browser, @sentry/node, @sentry/tracing and @sentry/vue packages. (#5040)
• Removed Angular, Ember, and Vue integrations from @sentry/integrations in favour of the explicit framework packages: @sentry/angular, @sentry/ember, and @sentry/vue. (#4893)
• Removed enums Status, RequestSessionStatus, and SessionStatus. Deprecated enums SpanStatus and Severity. This was done to save on bundle size. (#4891) (#4889) (#4890)
• Removed support for deprecated @sentry/apm package. (#4845)
• Removed deprecated user field from DSN interface. publicKey should be used instead. (#4864)
• Removed deprecated getActiveDomain method and DomainAsCarrier type from @sentry/hub. (#4858)
• Removed eventStatusFromHttpCode to save on bundle size.
• Removed usage of deprecated event.stacktrace field. (#4885)
• Removed raven-node backward-compat code (#4942)
• Removed showReportDialog method on BrowserClient (#4973)
• Removed deprecated startSpan and child methods (#4849)
• Removed deprecated frameContextLines options (#4884)
• Removed Sentry from window in the Gatsby SDK (#4857)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

7.0.0

Version 7 of the Sentry JavaScript SDK brings a variety of features and fixes including bundle size and performance improvements, brand new integrations, support for the attachments API, and key bug fixes.

This release does not change or remove any top level public API methods (captureException, captureMessage), and only requires changes to certain configuration options or custom clients/integrations/transports.

Note: The v7 version of the JavaScript SDK requires a self-hosted version of Sentry 20.6.0 or higher. If you are using a version of self-hosted Sentry (aka onpremise) older than 20.6.0 then you will need to upgrade.

For detailed overview of all the changes, please see our v7 migration guide.

Breaking Changes

If you are a regular consumer of the Sentry JavaScript SDK you only need to focus on the general items. The internal breaking changes are aimed at libraries that build on top of and extend the JavaScript SDK (like @sentry/electron or @sentry/react-native).

General

• Updated CommonJS distributions to use ES6 by default. If you need to support Internet Explorer 11 or old Node.js versions, we recommend using a preprocessing tool like Babel to convert Sentry packages to ES5. (#5005)
• Default bundle.min.js to ES6 instead of ES5. ES5 bundles are still available at bundle.es5.min.js. (#4958)
• Updated build system to use TypeScript 3.8.3 (#4895)
• Deprecated Severity enum for bundle size reasons. Please use string literals instead. (#4926)
• Removed critical Severity level. (#5032)
• whitelistUrls and blacklistUrls have been renamed to allowUrls and denyUrls in the Sentry.init() options. (#4850)
• BaseClient and it's child classes now require transport, stackParser, and integrations to be explicitly passed in. This was done to improve tree-shakability. (#4927)
• Updated package distribution structure and stopped distributing CDN bundles through @sentry/* npm packages. See details in our migration docs.. (#4900) (#4901)
• Simplified Transport API. This means custom transports will have to be adjusted accordingly..
• Updated how Node Transport Options are passed down.
• Start propogating baggage HTTP header alongside sentry-trace header to propogate additional tracing related information.. (#5133)
• Renamed registerRequestInstrumentation export to instrumentOutgoingRequests in @sentry/tracing. (#4859)
• Renamed UserAgent integration to HttpContext. (#5027)
• Replaced BrowserTracing integration's maxTransactionDuration option with finalTimeout option in the @sentry/tracing package and reset idleTimeout based on activities count. This should improve accuracy of web-vitals like LCP by 20-30%. (#5044)
• Updated @sentry/angular to be compiled by the angular compiler. (#4641)
• Made tracing package treeshakable (#5166)
• Removed support for Node v6. (#4851)
• Removed @sentry/minimal package in favour of using @sentry/hub. (#4971)
• Removed support for Opera browser pre v15 (#4923)
• Removed ignoreSentryErrors option from AWS lambda SDK. Errors originating from the SDK will now always be caught internally. (#4994)
• Removed Integrations.BrowserTracing export from @sentry/nextjs. Please import BrowserTracing from @sentry/nextjs directly.
• Removed static id property from BrowserTracing integration.
• Removed SDK_NAME export from @sentry/browser, @sentry/node, @sentry/tracing and @sentry/vue packages. (#5040)
• Removed Angular, Ember, and Vue integrations from @sentry/integrations in favour of the explicit framework packages: @sentry/angular, @sentry/ember, and @sentry/vue. (#4893)
• Removed enums Status, RequestSessionStatus, and SessionStatus.. Deprecated enums SpanStatus and Severity. This was done to save on bundle size. (#4891) (#4889) (#4890)
• Removed support for deprecated @sentry/apm package. (#4845)
• Removed deprecated user field from DSN interface. publicKey should be used instead. (#4864)
• Removed deprecated getActiveDomain method and DomainAsCarrier type from @sentry/hub. (#4858)
• Removed eventStatusFromHttpCode to save on bundle size.
• Removed usage of deprecated event.stacktrace field. (#4885)
• Removed raven-node backward-compat code (#4942)
• Removed showReportDialog method on BrowserClient (#4973)
• Removed deprecated startSpan and child methods (#4849)
• Removed deprecated frameContextLines options (#4884)

... (truncated)

Commits

• 4cc07f6 release: 7.0.0
• ca31aa3 meta: 7.0.0 CHANGELOG (#5177)
• 31be2be ref(node): Allow node stack parser to work in browser context (#5135)
• 8fcf3ff release: 7.0.0-rc.0
• c946b23 meta: Update 7.0.0-rc.0 CHANGELOG (#5165)
• 0e1f578 feat(nextjs): Make tracing package treeshakable (#5166)
• e76c247 ref(build): Use rollup to build AWS lambda layer (#5146)
• 9b23ef3 ref(core): Test mutation of attachments in hint (#5140)
• 918d470 fix(utils): Fix infinite recursion in dropUndefinedKeys (#5163)
• bc73dc0 ref(core): Make hint callback argument non-optional (#5141)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by sentry-bot, a new releaser for @​sentry/browser since your current version.

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 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)

[codecov[bot]]

Codecov Report

Merging #600 (73c2fec) into development (5c0252e) will not change coverage. The diff coverage is n/a.

@@             Coverage Diff              @@
##           development     #600   +/-   ##
============================================
  Coverage        92.54%   92.54%           
============================================
  Files               94       94           
  Lines             2254     2254           
============================================
  Hits              2086     2086           
  Misses             168      168           

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 5c0252e...73c2fec. Read the comment docs.

[dependabot[bot]]

Superseded by #604.