Repository navigation
Vercel Edge Runtime Stack Traces #6805
Description
Problem Statement
The stack traces on the Vercel Edge runtime still look horrible. They seem to flow through some kind of sandbox and aren't source mapped at all.
Solution Brainstorm
We should first try to source map the events somehow by uploading the right files. If we don't come to a solution we can collaborate with the Vercel folks.
Reacted by mrpatrickpilch
Reacted by mrpatrickpilch and David Santucci
Activity
vojto commentedon Nov 6, 2023
Is there no way to get stack traces in edge functions currently? This is what ours look like:
lforst commentedon Nov 6, 2023
No, unfortunately not. However, it is on our very-short-term roadmap. I might even start working on it today!
lforst commentedon Nov 6, 2023
Ok, good news and bad news.
I just chatted with some people from Vercel and they said they bundle the edge functions an additional time when deploying. This means the SDK doesn't have the opportunity to upload the newly (Vercel) bundled files + sourcemaps to Sentry.
We'll brainstorm a solution for this!
[-]Next.js Edge Runtime Stack Traces[/-][+]Vercel Edge Runtime Stack Traces[/+]lforst commentedon Nov 14, 2023
Issue on the vercel repo for context: vercel/vercel#10829
3 remaining items
lforst commentedon Dec 20, 2023
@jenwoodson Yes you are running into the same issue. Stack traces and source maps on Vercel are inherently broken for tools like Sentry and to fix this, Vercel would need to provide a way to access the source maps they generate after they run their additional (hidden) bundling step.
You can follow this issue for progress: vercel/vercel#10829