Issue
Some stack trace frames from third-party or vendor code in my app stay minified. Source maps work for my own files, but not for those outside frames.
Applies To
All SaaS Customers and Self-Hosted Users
JavaScript SDK
Source maps
Stack Trace Rules
Error Monitoring
Resolution
Frames from code outside your app’s source map upload often stay unmapped. That is expected when you ship pre-built third-party bundles (for example a chat widget) that were not produced by your build and were not uploaded with matching source maps.
If that third-party code is compiled in your bundler and you upload source maps for those artifacts, Sentry can map those frames. If it is loaded as an external / pre-built script without maps in your project, Sentry cannot unminify it.
When you do not need those frames for debugging or grouping, use Stack Trace Rules in Project Settings → Issue Grouping to mark them out of app and/or out of grouping. For example:
# Mark vendor paths as not in-app and exclude them from grouping stack.abs_path:**/vendor/** -app -group stack.abs_path:**/node_modules/** -app -group
Actions like -app and -group (and “cut” patterns with ^ / v) change how Sentry classifies frames and how event grouping uses them. They do not create source maps for third-party code.