Sourcemaps not applied (minimal repo)
See original GitHub issueHi,
I am trying to get the client-side source maps applied on Sentry without success. I made a minimal repo to illustrate the problem: https://github.com/verekia/sentry-sourcemaps
Here is a link to an event: https://sentry.io/organizations/jonathan-verrecchia/issues/1223237123/
And some screenshots:





What am I doing wrong here? 😃
I’ve tried urlPrefix
, putting my files at the root. Nothing seems to affect the result on Sentry.
Thank you very much.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
sourcemaps are detected but not working in chrome-extension ...
"sourcemaps are detected" message is shown in the sources tab but the original source files are not listed. if the page is loaded...
Read more >chrome 72 changes sourcemap behaviour - Stack Overflow
After updating from Chrome 70 to 72, sourcemaps no longer work. As a minimal example, I can reproduce the problem on MacOS 14...
Read more >Build Performance - webpack
Apply loaders to the minimal number of modules necessary. Instead of: ... Custom plugins/loaders. Profile them to not introduce a performance problem here....
Read more >Source-maps could be revealing your private project files
When you publish your minified JavaScript files to your server, your source-maps could be published also by mistake, which means that everyone ...
Read more >Upload JavaScript Source Maps - Datadog Docs
Datadog can also link stack frames to your source code in your repository. ... each source map augmented with the size of the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I guess it helps. Maybe having a link to that specific section of this page on the Webpack plugin’s Readme would help. It’s just that in this kind of project, there are so many different “paths” of everything, that it’s easy to lose track.
output
of Webpack/
urlPrefix
, starting with~/
include
~/
but/
It easily gets mixed up and can be quite confusing. I feel like it’s better to over-document than under-document these things.
Also, the
import
syntax works correctly on Sentry after a Babel transformation.