Uh oh!
There was an error while loading. Please reload this page.
fix(nextjs): Don't inject trace meta tags when Cache Components is enabled - #21141
Merged
Conversation
Contributor
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you apply the label |
…s-streaming # Conflicts: # dev-packages/e2e-tests/test-applications/nextjs-16-cacheComponents/tests/cacheComponents.spec.ts
Resolves the dependency-review failure caused by pinning a vulnerable next 16.2.3. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
size-limit report 📦
|
chargome
marked this pull request as ready for review
June 30, 2026 13:54
chargome
requested review from
logaretm, mydea, nicohrubec and s1gr1d
and removed request for
a team and mydeaJune 30, 2026 13:54
logaretm
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem is that we do not have a consistent way of detecting stale meta tags so we rather disable them for
cacheComponents.This stops the SDK from enabling Next's
experimental.clientTraceMetadata(sentry-trace/baggage) whencacheComponentsis enabled. With no meta tags injected, the browser pageload starts a fresh, self-contained trace instead of stitching onto a stale one. Apps that don't use Cache Components are unaffected.closes https://linear.app/getsentry/issue/JS-2782/cachecomponents-setup-breaks-meta-tag-injection