Run the React Router e2e suite on Bun, Deno and Cloudflare from one app

[JPeer264]

Run the React Router e2e suite on Node, Bun, Deno and Cloudflare from one app. Node stays the required job; Bun, Deno and Cloudflare are optional variants that become required once green.

Apps

• Base: react-router-8-framework
• Fold in, then delete: react-router-8-cloudflare

#24598 adds the Bun, Deno and Cloudflare variants to react-router-8-framework and fixes the SDK bugs they surfaced. This issue tracks it to the merge and the deletion of react-router-8-cloudflare.

Cover on every runtime

The existing suite runs unchanged and branches on RUNTIME only where runtimes are expected to differ. Add assertions where the suite has none today:

• Errors
• Parameterized route names
• Per-request isolation
• Incoming trace continuation
• Outgoing fetch with sentry-trace and baggage
• Logs

Findings to confirm (runtime audit, September 2026, develop 6f2da7483d; database spans were measured with mysql or mysql2):

• Bun: route names: broken; isolation: broken; incoming trace: broken; outgoing fetch: broken; db spans: broken. test(bun): Run the auto-instrumentation suites with bundled scenarios #24612 targets the missing request span on Bun.
• Deno: outgoing fetch: broken; db spans: partial. deno: Outgoing fetch gets no span and no trace propagation #23891 has added outgoing fetch spans to @sentry/deno since.
• Cloudflare: everything measured worked.

Setups the audit ran: Bun, Deno, Cloudflare

Done when

• react-router-8-framework runs its suite on Node, Bun, Deno and Cloudflare
• Every variant is green and required, or this issue records why a runtime is not supported
• react-router-8-cloudflare is deleted
• SDK defects the variants surface are fixed here, or split into their own issue when the fix is large or shared with other libraries

[linear-code]

JS-3837