Skip to content

test(e2e): Port React Router v5 and v6 E2E apps to span streaming - #23841

Open
andreiborza wants to merge 1 commit into
ab/js-3482/static-coveragefrom
ab/js-3482/react-router-v5-v6
Open

test(e2e): Port React Router v5 and v6 E2E apps to span streaming#23841
andreiborza wants to merge 1 commit into
ab/js-3482/static-coveragefrom
ab/js-3482/react-router-v5-v6

Conversation

@andreiborza

@andreiborza andreiborza commented Sep 1, 2026

Copy link
Copy Markdown
Member

What

Ports react-router-5, react-router-6, react-router-6-use-routes and react-router-6-descendant-routes to span streaming.

Why

Span streaming is the default now, so the E2E suite has to exercise it. The SSE spec needed more than a helper swap: a streamed http.client span carries only the domain in its name, so the request is matched on url.full, and the abort error is read off the console because spans carry no breadcrumbs.

Part of #23798

@linear-code

linear-code Bot commented Sep 1, 2026

Copy link
Copy Markdown

JS-3482

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

size-limit report 📦

Path Size % Change Change
@sentry/browser 28.57 kB - -
@sentry/browser - with treeshaking flags 26.94 kB - -
@sentry/browser - with treeshaking flags tracing without tracing 26.83 kB - -
@sentry/browser (incl. Tracing) 48.87 kB - -
@sentry/browser (incl. Tracing + Span Streaming) 48.88 kB - -
@sentry/browser (incl. Tracing, Profiling) 51.8 kB - -
@sentry/browser (incl. Tracing, Replay) 88.36 kB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 77.76 kB - -
@sentry/browser (incl. Tracing, Replay with Canvas) 93.05 kB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 106.02 kB - -
@sentry/browser (incl. Feedback) 46.06 kB - -
@sentry/browser (incl. sendFeedback) 33.64 kB - -
@sentry/browser (incl. FeedbackAsync) 38.74 kB - -
@sentry/browser (incl. Metrics) 29.52 kB - -
@sentry/browser (incl. Logs) 29.81 kB - -
@sentry/browser (incl. Metrics & Logs) 30.45 kB - -
@sentry/react 30.32 kB - -
@sentry/react (incl. Tracing) 51.08 kB - -
@sentry/vue 35.74 kB - -
@sentry/vue (incl. Tracing) 51.14 kB - -
@sentry/svelte 28.6 kB - -
CDN Bundle 30.36 kB - -
CDN Bundle (incl. Tracing) 49.52 kB - -
CDN Bundle (incl. Logs, Metrics) 32.59 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) 51.43 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) 73.19 kB - -
CDN Bundle (incl. Tracing, Replay) 87.01 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 88.88 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 92.94 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 94.84 kB - -
CDN Bundle - uncompressed 89.97 kB - -
CDN Bundle (incl. Tracing) - uncompressed 147.58 kB - -
CDN Bundle (incl. Logs, Metrics) - uncompressed 96.27 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 153.27 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 225.43 kB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 267.07 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 272.75 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 280.77 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 286.44 kB - -
@sentry/nextjs (client) 53.7 kB - -
@sentry/sveltekit (client) 49.3 kB - -
@sentry/core/server 40.74 kB - -
@sentry/core/browser 13.42 kB - -
@sentry/node 123.87 kB +0.02% +19 B 🔺
@sentry/node/import (ESM hook with diagnostics-channel injection) 81.4 kB - -
@sentry/node - without tracing 88.2 kB +0.03% +22 B 🔺
@sentry/node - without channel injection 103.31 kB +0.02% +16 B 🔺
@sentry/aws-serverless 96.56 kB +0.03% +21 B 🔺
@sentry/cloudflare (withSentry) - minified 201.23 kB - -
@sentry/cloudflare (withSentry) 500.94 kB - -

View base workflow run

'sentry.origin': { value: 'auto.navigation.react.reactrouter_v6', type: 'string' },
'sentry.segment.name.source': { value: 'route', type: 'string' },
'url.template': { value: '/bar/:barId', type: 'string' },
'url.path': { value: '/bar/456', type: 'string' },

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

super-l: should we also assert against url.full here? Just noticed we do so below but feel free to skip

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added it, the original test omitted it there but there is no reason to.

@andreiborza
andreiborza force-pushed the ab/js-3482/react-router-v5-v6 branch from d87c67b to b0f464f Compare September 1, 2026 16:51

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit b0f464f. Configure here.

@andreiborza
andreiborza force-pushed the ab/js-3482/react-router-v5-v6 branch from b0f464f to 37956c8 Compare September 2, 2026 08:23
Removes the `traceLifecycle: 'static'` pin from `react-router-5`,
`react-router-6`, `react-router-6-use-routes` and
`react-router-6-descendant-routes`, and rewrites their specs against streamed
span v2.

The `react-router-6` SSE spec needed more than a helper swap: streamed
`http.client` names carry only the domain, so the request is matched on
`url.full`, and the abort error is read off the console because spans carry no
breadcrumbs. All three SSE tests load the same route, so each one also pins its
lookup to a pageload span that started after it navigated.
@andreiborza
andreiborza force-pushed the ab/js-3482/react-router-v5-v6 branch from 37956c8 to b24c46c Compare September 2, 2026 08:46
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.

3 participants