Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(nextjs): Export BrowserTracing integration directly #4480

Merged
merged 1 commit into from
Feb 1, 2022

Conversation

lobsterkatie
Copy link
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
Contributor

github-actions bot commented Feb 1, 2022

size-limit report

Path Base Size (86fa701) Current Size Change
@sentry/browser - CDN Bundle (gzipped) 19.68 KB 19.68 KB +0.01% 🔺
@sentry/browser - CDN Bundle (minified) 62.89 KB 62.9 KB +0.01% 🔺
@sentry/browser - Webpack 22.21 KB 22.21 KB 0%
@sentry/browser - Webpack - gzip = false 76.02 KB 76.02 KB 0%
@sentry/react - Webpack 22.24 KB 22.24 KB 0%
@sentry/nextjs Client - Webpack 46.23 KB 46.23 KB 0%
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped) 28.22 KB 28.23 KB +0.02% 🔺

@lobsterkatie lobsterkatie merged commit 1214a03 into master Feb 1, 2022
@lobsterkatie lobsterkatie deleted the kmclb-nextjs-export-browsertracing-directly branch February 1, 2022 18:11
Sign up for free to 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