Unresolved source maps with Vercel CLI #13766
Description
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
8.29.0
Framework Version
No response
Link to Sentry event
No response
Reproduction Example/SDK Setup
No response
Steps to Reproduce
A customer deploys their next app in a Github Action on tag, so it’s not a common deployment in Vercel. They use Vercel CLI instead. Their setup is attached in the shadow ticket.
This is a continuation of this Slack conversation.
Expected Result
Events have readable stack traces.
Actual Result
Some static/chunks source maps are missing even though they have widenClientFileUpload: true, and so they cannot be applied to the events.
┆Issue is synchronized with this Jira Improvement by Unito