Issue
After I upload source maps from a Vercel deployment, Sentry still shows minified stack traces for Next.js Edge Function events. Frames look like vc/edge/function instead of my original file names and line numbers. I expected readable code after source map upload.
Applies To
All SaaS Customers and Self-Hosted Users
Next.js SDK
Vercel
Source maps
Resolution
Vercel Edge Function stack traces cannot be source-mapped when the frames show vc/edge/function. Vercel bundles edge functions again after your Next.js build, and that second bundle is not available to Sentry.
If your stack frames show vc/edge/function:
This is a Vercel platform limitation, not a failed Sentry source map upload. The Next.js SDK still uploads edge source maps from next build. Those maps do not match the bundle Vercel deploys.
If the same error looks readable locally or on the Node.js runtime:
That confirms the limitation is specific to Vercel’s extra edge bundling step.
If you need readable stack traces:
Run the route on the Node.js runtime instead of the Edge runtime. Client and Node.js server events still use uploaded source maps. See the Next.js source maps documentation.
If the frames are minified but do not say vc/edge/function:
Follow the source maps troubleshooting guide. The Vercel edge limitation does not apply.
Sentry reported this to Vercel in a GitHub issue and a Vercel Community post. Those resources are not built or maintained by Sentry. Vercel has not shipped a way for third-party tools to consume the post-deploy edge source maps.