Skip to content

fix(nextjs): Export BrowserTracing integration directly - #4480

Merged
lobsterkatie merged 1 commit into
masterfrom
kmclb-nextjs-export-browsertracing-directly
Feb 1, 2022
Merged

fix(nextjs): Export BrowserTracing integration directly#4480
lobsterkatie merged 1 commit into
masterfrom
kmclb-nextjs-export-browsertracing-directly

Conversation

@lobsterkatie

Copy link
Copy Markdown
Member

This applies the changes made in #4204 (exporting BrowserTracing outside of Integrations, in order that it be treeshakable if necessary) to the nextjs SDK, which got left out of that PR.

Fixes#4411.

@github-actions

Copy link
Copy Markdown
Contributor

size-limit report

PathBase Size (86fa701)Current SizeChange
@sentry/browser - CDN Bundle (gzipped)19.68 KB19.68 KB+0.01% 🔺
@sentry/browser - CDN Bundle (minified)62.89 KB62.9 KB+0.01% 🔺
@sentry/browser - Webpack22.21 KB22.21 KB0%
@sentry/browser - Webpack - gzip = false76.02 KB76.02 KB0%
@sentry/react - Webpack22.24 KB22.24 KB0%
@sentry/nextjs Client - Webpack46.23 KB46.23 KB0%
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped)28.22 KB28.23 KB+0.02% 🔺

@lobsterkatie
lobsterkatie merged commit 1214a03 into masterFeb 1, 2022
@lobsterkatie
lobsterkatie deleted the kmclb-nextjs-export-browsertracing-directly branch February 1, 2022 18:11
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sentry-trace header being added to request to origin not in tracingOrigins

2 participants

@lobsterkatie@AbhiPrasad