Reproduction for sentry-javascript#19013

[Lms24]

Summary

Reproduction for getsentry/sentry-javascript#19013

This reproduces the scope isolation issue when using @sentry/bun with Express:

• Incoming HTTP requests don't get properly scoped
• No trace IDs are generated for Express request handlers
• Multiple requests share the same (absent) trace context instead of each having unique trace IDs

How to run

cd sentry-javascript/19013
bun install
bun run start
# In another terminal:
bun run test

Observed behavior

=== Results ===

Request 1: endpoint1 -> Trace ID: NO TRACE ID
Request 2: endpoint2 -> Trace ID: NO TRACE ID
...

=== Summary ===

Total requests: 6
Unique trace IDs: 0

❌ BUG: No trace IDs were generated at all

Expected behavior

Each incoming HTTP request should have its own unique trace ID, with automatic instrumentation creating new root spans for each request.

[cursor]

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

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

node_modules directory accidentally committed to repository

Medium Severity

The node_modules directory has been committed to the repository. This significantly bloats the repository with dependency files that can be regenerated from bun.lock. The lock file already captures exact dependency versions, making committed node_modules unnecessary for reproduction purposes.

Additional Locations (1)

• sentry-javascript/19013/node_modules/@apm-js-collab/code-transformer/LICENSE#L1-L202