New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source Map is generated, loaded by browser (HTTP 200), but does not work. #266
Comments
I have the same issue, the sourcemaps are being loaded, but chrome isn't making "the connection". I think this is related to the removal of some options related to custom paths, that now are being calculated automatically. |
Well, I don't think it is directly related to that change, since I tried on both old and new versions, outcome is the same. |
+1 Do your maps throw an error when parsed by the BASE64 VLQ CODEC http://murzwin.com/base64vlq.html
I've also tried serving |
Or is it related to this issue #270? |
Experiencing the same issue
|
Same here:
|
Same here: But I'm using webpack, so this might be a red herring? |
jQuery source map also produces the same error: By the way, my problems were solved by upgrading all my npm modules to the latest versions. So I am not sure what exactly the problem was. |
has anyone figured this out? |
There have been fixes to source-map on Please report to https://github.com/mishoo/UglifyJS2/issues with reproducible test case if this is still an issue. |
Hi everyone,
I am experiencing weird issue with uglify/sourceMap feature.
Generally, source map is generated, loaded by browser (HTTP 200), but does not work (in the "Sources" tab of Chrome, everything still looks minified/uglified). At the same time other sourcemaps (on another project) are working well.
Here is my grunt uglify configuration:
what it does is uglify/minify+sourcemap of 1 file (which is located at build/bootstraps/bootstrap.js).
Yes, it uglifies itself (since it is result of multi-step process).
I tried to separate, same result.
Here is what generated:
bootstrap.js:
bootstrap.js.map:
Can you please suggest any direction where the issue can be?
The text was updated successfully, but these errors were encountered: