Skip to content

Warn for duplicate browserTracingIntegrations #16040

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.

Sign up for GitHub

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

Jump to bottom
Closed
mydea opened this issue Apr 14, 2025 — with Linear · 1 comment · Fixed by #16042
Closed

Warn for duplicate browserTracingIntegrations #16040

mydea opened this issue Apr 14, 2025 — with Linear · 1 comment · Fixed by #16042
Assignees
@mydea
Labels
Improvement Package: browser Issues related to the Sentry Browser SDK

Comments

@mydea Linear
Copy link
Member

mydea commented Apr 14, 2025

Based on #16028, we should warn if multiple types of browserTracingIntegration are added. this can happen if you e.g. follow the react docs, where we tell you to replace the default one with the more specific react router one. If users leave the generic one in, weird things may happen.
@mydea mydea added Improvement Package: browser Issues related to the Sentry Browser SDK labels Apr 14, 2025 — with Linear
@mydea mydea self-assigned this Apr 14, 2025
This was referenced Apr 14, 2025
Merged
Closed
@mydea mydea closed this as completed in bd7205b Apr 14, 2025
@github-actions GitHub Actions
Copy link
Contributor

A PR closing this issue has just been released 🚀

This issue was referenced by PR #16042, which was included in the 9.13.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mydea mydea

Labels
Improvement Package: browser Issues related to the Sentry Browser SDK
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(browser): Warn on duplicate browserTracingIntegration getsentry/sentry-javascript
1 participant
@mydea