This is a copy paste from https://github.com/vercel/vercel/issues/10829 which got closed but I was told to post here.

GitHub

Vercel Edge Runtime Source Maps not accessible for 3rd party consumption · Issue #10829 · vercel/vercel

I don't have full insights into this on Vercel's side so some of the following are assumptions. Context Third-party tools like Sentry would like to access source maps for a running application so t...

I don't have full insights into this on Vercel's side so some of the following are assumptions.

Context

Third-party tools like Sentry would like to access source maps for a running application so that stack traces for logged errors can be source-mapped.

Problem

Since functions deployed on the Vercel Edge Runtime are bundled in an additional step opaquely, there is no way for any SDKs to pick up the source maps to upload them to third-party services. This will make it impossible to trace the errors back to their original location. Currently stack traces look like this:

1
Error: Edge Stack Traces
2
    at (vc/edge/function:122:5661)
3
    at (vc/edge/function:125:10587)
4
    at (vc/edge/function:122:5622)
5
    at (vc/edge/function:147:11182)
6
    at (vc/edge/function:147:9157)
7
    at (vc/edge/function:147:11007)
8
}

Solution brainstorm

• No additional bundling steps after building a Next.js application. (I don't know if feasible)
• Expose source maps to the runtime via some global variable. (probably would introduce too much memory overhead)
• Expose sourcemaps on a separate service (like S3) behind an auth token. Out of these, this is the approach that makes the most sense.