Cannot upload Cloudflare worker.js sourcemaps when using OpenNext

[Livijn]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

10.34.0

Framework Version

Next 15.5.9 (OpenNext + Cloudflare Workers)

Link to Sentry event

https://dogs-unleashed-ab.sentry.io/issues/93718351/events/f3276ea43fa8497c8d2ff2f00fa645eb/

Reproduction Example/SDK Setup

App is a Next 15.5.9 Pages app deployed via OpenNext to Cloudflare Workers.

Setup summary:

• Build: opennextjs-cloudflare build
• Wrangler build output: wrangler deploy --outdir .wrangler-sourcemaps --upload-source-maps ...
• Debug IDs injected: sentry-cli sourcemaps inject .wrangler-sourcemaps
• Upload: sentry-cli sourcemaps upload --debug-id-reference --rewrite .wrangler-sourcemaps
• Worker deployed using the same bundle (no re-bundling):
  wrangler deploy .wrangler-sourcemaps/worker.js --no-bundle ...

Artifacts are uploaded and visible in Sentry, including ~/worker.js and ~/worker.js.map with Debug IDs.

Steps to Reproduce

1. Deploy Next 15.5.9 using OpenNext on Cloudflare Workers.
2. Generate + upload sourcemaps for worker.js with Debug IDs (sentry-cli inject + upload).
3. Trigger an error in getServerSideProps.

Expected Result

Readable stack traces mapped to original source (e.g., pages/sentry-server-test.tsx).

Actual Result

Sentry still shows worker.js frames and says:

• “Stack frame doesn’t have Debug IDs”
• “Uploaded files not deployed”

Example (screenshot):

Additional Context

I can confirm:

• Debug IDs exist in worker.js and worker.js.map.
• The deployed worker file is the same artifact used for upload.
• Sentry release is set and consistent.

Seems like the runtime frames in the event don’t include Debug IDs, even though the bundle contains them. Is @sentry/nextjs (or OpenNext) stripping debug ID metadata in the runtime stack frames for Cloudflare Workers?

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1655

[andreiborza]

Hey @Livijn, thanks for raising this as a follow up.

@logaretm I assigned you since you were looking into it.

[jcohenho]

@logaretm I am also experiencing this in my NextJS + SST setup:

If I try to deploy with withSentryConfig(nextConfig, {...}) enabled in next.config.js, I get the following error:

┌──────────────────────────────┐
│ OpenNext — Generating bundle │
└──────────────────────────────┘

Bundling middleware function...
Bundling static assets...
Bundling cache assets...
Building server function: default...
file:///private/var/folders/cz/2jxz3hfs1w7czmcp87d0l50c0000fn/T/open-next-tmpbgBnDF/next.config.mjs:11
  throw Error('Dynamic require of "' + x + '" is not supported');
        ^

Error: Dynamic require of "fs" is not supported

[logaretm]

@jcohenho could you create a new issue for this to avoid hijacking the original issue here?