You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)@sentry/tracing
6.2.0Description
Instead of being able to
import { BrowserTracing } from "@sentry/tracing"
directly, you need toimport { Integrations } from "@sentry/tracing"
, and then get it viaIntegrations.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
.The text was updated successfully, but these errors were encountered: