Skip to content

test(e2e): Add a static trace lifecycle React Router E2E app - #23840

Merged
andreiborza merged 1 commit into
developfrom
ab/js-3482/static-coverage
Sep 2, 2026
Merged

test(e2e): Add a static trace lifecycle React Router E2E app#23840
andreiborza merged 1 commit into
developfrom
ab/js-3482/static-coverage

Conversation

@andreiborza

@andreiborza andreiborza commented Sep 1, 2026

Copy link
Copy Markdown
Member

What

Adds react-router-7-framework-static, a copy of react-router-7-framework that keeps traceLifecycle: 'static' and its transaction-based specs.

Why

The rest of the React Router E2E group moves to span streaming in the PRs above this one, so this copy is what keeps the static trace lifecycle covered. The issue suggested duplicating react-19, but react-router-7-framework is the app in this group with the most server and client instrumentation to keep covered. The copy drops the latest build variant, so it costs one CI job rather than two.

Being a verbatim copy, review bots flag pre-existing issues in it as if they were new. Those live in react-router-7-framework on develop too and are better fixed in both apps separately.

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 124.05 kB +0.02% +23 B 🔺
@sentry/node/import (ESM hook with diagnostics-channel injection) 81.51 kB - -
@sentry/node - without tracing 88.3 kB +0.03% +21 B 🔺
@sentry/node - without channel injection 103.35 kB +0.02% +18 B 🔺
@sentry/aws-serverless 96.66 kB +0.03% +24 B 🔺
@sentry/cloudflare (withSentry) - minified 201.23 kB - -
@sentry/cloudflare (withSentry) 500.94 kB - -

View base workflow run

@andreiborza
andreiborza force-pushed the ab/js-3482/static-coverage branch 4 times, most recently from 6817d85 to d41e1c4 Compare September 2, 2026 09:05

@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 d41e1c4. Configure here.

@andreiborza
andreiborza force-pushed the ab/js-3482/static-coverage branch from d41e1c4 to e83f714 Compare September 2, 2026 09:30
@andreiborza
andreiborza changed the base branch from develop to ab/js-3482/collect-streamed-spans September 2, 2026 09:31
An error occurred while trying to automatically change base from ab/js-3482/collect-streamed-spans to develop September 2, 2026 09:57
@andreiborza
andreiborza force-pushed the ab/js-3482/static-coverage branch from e83f714 to 3f2afd6 Compare September 2, 2026 10:01
@andreiborza
andreiborza changed the base branch from ab/js-3482/collect-streamed-spans to develop September 2, 2026 10:01
Copies `react-router-7-framework` into `react-router-7-framework-static`, which
keeps `traceLifecycle: 'static'` and its transaction-based specs. The rest of the
React Router group moves to span streaming in the PRs above, so this copy is what
keeps the static lifecycle covered.

The copy drops the `latest` build variant, so it costs one CI job rather than two.
@andreiborza
andreiborza force-pushed the ab/js-3482/static-coverage branch from 3f2afd6 to 436f969 Compare September 2, 2026 10:07
@andreiborza
andreiborza merged commit a0ad6f5 into develop Sep 2, 2026
43 checks passed
@andreiborza
andreiborza deleted the ab/js-3482/static-coverage branch September 2, 2026 11:18
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