-
We upload source maps after this guide for webpack, although we have to manually create some source maps with Encore
.configureTerserPlugin((options) => {
options.minify = async (input, sourceMap) => { // `async` for speed.
const filename = Object.keys(input)[0];
let code = input[filename];
let map = sourceMap;
// REASONING:
// Because our "static" JavaScript modules are not added as webpack "entry points", they are not resolved as `SourceMapSource` internally, meaning webpacks SourceMapDevToolPlugin will not "attach" their source maps (although they are generated).
// I don't know why SourceMapDevToolPlugin is not attaching these, for details of the investigation see https://github.com/webpack/webpack/discussions/19167 .
if (filename.includes('/') && !map) {
let minified = require('uglify-js').minify(input, {
sourceMap: {
filename: filename, // Used for "file" attribute in source map.
includeSources: true, // Used for "sourcesContent" attribute in source map.
}
});
code = minified.code;
map = minified.map;
}
return {code, map, warnings: [], errors: [], extractedComments: []};
}
}) We then upload sourcemaps with
As suggested in the docs, we remove the source maps after uploading them, although I use But now we get As sentry should resolve source maps in the sentry application, not in the users browser, I have no idea why the symbolicator creates these requests. Why does Symbolicator requests source maps in our case? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
It's not the SDK or Sentry requesting the source map. It's your browser. Whenever you have a You can tell uglify not to emit a |
Beta Was this translation helpful? Give feedback.
As you commented #12463 (comment), it is likely that setting you said (as I can see the
User-Agent
header issymbolicator...
), right?