You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 271954d
Browse filesBrowse the repository at this point in the historyBrowse files
test(e2e): Run express-5 on Bun, Deno and Cloudflare
Renames `node-express-v5` to `express-5` and adds optional Bun, Deno and
Cloudflare variants next to the required Node job. Each runtime inits
its own SDK, and the app reads the Sentry API from `src/sentry.ts`, which
each variant replaces with its SDK.
- Node still runs the CommonJS build. `src/main.ts` is the entry now, so
that the Worker can import the app without the Node init.
- Bun bundles `src/main.ts` with `@sentry/bun/plugin`.
- Deno runs the TypeScript sources with `--preload=@sentry/deno/import`.
- Cloudflare builds with Vite and `sentryCloudflareVitePlugin`. The app
registers its routes at module scope, like the Express docs show.
New tests cover parameterized route names, per-request isolation,
incoming trace continuation and outgoing `fetch` propagation. They pass
on all four runtimes without a `RUNTIME` branch.
Tests that branch on `RUNTIME`:
- Local variables and the Node runtime metrics run on Node only.
- The MCP SSE transport is skipped on Cloudflare. workerd cancels the
write to the response of another request, also without Sentry.
- The `http.server` span has no `http.response.status_text` on Bun, and
comes from the Worker `Request` on Cloudflare.
The MySQL route opens its connection in the request, because on
Cloudflare a socket only works in the request that opened it.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
0 commit comments