feat(nextjs): Register a route provider outside the tracing integration - #23552
Draft
logaretm wants to merge 1 commit into
Draft
feat(nextjs): Register a route provider outside the tracing integration#23552logaretm wants to merge 1 commit into
logaretm wants to merge 1 commit into
Conversation
5 tasks
Contributor
size-limit report 📦
|
logaretm
force-pushed
the
awad/route-provider-nextjs
branch
2 times, most recently
from
August 24, 2026 20:17
737c9cf to
5d8e20b
Compare
logaretm
force-pushed
the
awad/route-provider-nextjs
branch
from
August 24, 2026 20:52
5d8e20b to
464c7d0
Compare
logaretm
force-pushed
the
awad/route-provider-nextjs
branch
from
August 24, 2026 20:57
464c7d0 to
1eb7910
Compare
logaretm
force-pushed
the
awad/route-provider-nextjs
branch
2 times, most recently
from
August 31, 2026 17:05
21288e6 to
fec1a68
Compare
logaretm
changed the base branch from
awad/route-provider-api
to
awad/route-provider-tracing-naming
August 31, 2026 17:13
logaretm
force-pushed
the
awad/route-provider-nextjs
branch
from
August 31, 2026 18:19
fec1a68 to
7016bab
Compare
logaretm
changed the base branch from
awad/route-provider-tracing-naming
to
awad/route-provider-api
August 31, 2026 18:19
Both routers already ship a pure matcher: the App Router has the build-time route manifest behind `maybeParameterizeRoute`, and the Pages Router matches against `__BUILD_MANIFEST.sortedPages`. Neither was reachable from anywhere except the pageload and navigation instrumentation. Registered from `init()` rather than `browserTracingIntegration`, because both manifests are on the global object before `Sentry.init` runs. Route parameterization no longer depends on tracing being enabled, so `bfcacheMetrics` resolves a parameterized route with `browserTracingIntegration` absent. The two manifests want the pathname differently, since App Router routes are generated with `basePath` baked in while Next strips it internally for the Pages Router, so the provider normalizes per manifest.
logaretm
force-pushed
the
awad/route-provider-nextjs
branch
from
August 31, 2026 18:28
7016bab to
fb24bbd
Compare
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Registers a route provider for Next.js from the manifests already injected at build time, covering both the App Router and the Pages Router.
Registered from
init()rather than frombrowserTracingIntegration, which is the point of the change: both manifests are on the global object beforeSentry.initruns, so nothing has to wait for a router or for tracing.bfcacheMetricsIntegrationnow resolves a parameterized route withbrowserTracingIntegrationabsent entirely, and the same will hold for web vitals and interactions as they move over.The two manifests want the pathname differently, since App Router routes are generated with
basePathbaked in while Next strips it internally for the Pages Router, so the provider normalizes per manifest.Part of #23556