@sentry/tracing Integrations can't be tree-shaked effectively

[osdiab]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
  • related issue: Package size is massive #2707
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other: @sentry/tracing 6.2.0

Description

Instead of being able to import { BrowserTracing } from "@sentry/tracing" directly, you need to import { Integrations } from "@sentry/tracing", and then get it via Integrations.BrowserTracing.

The result is that my bundle, despite having tree-shaking turned on, ends up including all the integrations, including mongo, postgres, etc - totally irrelevant to my browser web-app.

To avoid a breaking change I suggest just also exporting all the integrations as named members from the @sentry/tracing package, or alternatively exporting them from a separate sub-package like @sentry/tracing/integrations.

[osdiab]

ah i see now that i can just require it directly:

import { BrowserTracing } from "@sentry/tracing/dist/browser";

closing!