Replies: 1 comment
|
Hi, I don't think the issue is that Chrome only supports one inline source map. Each JavaScript file can have its own sourceMappingURL and DevTools should be able to handle multiple inline source maps. I would first check the generated files themselves and make sure each one ends with its own //# sourceMappingURL=data:... comment. Also check whether the two files are actually being generated with different source map metadata such as file or sources. If both files contain the inline map but DevTools only shows one, it could be related to how the files are being served or identified rather than sourceMapMode itself. Testing the same generated files as separate static resources would help isolate whether the problem comes from javascript-obfuscator or the browser/dev-server. |
Uh oh!
There was an error while loading. Please reload this page.
Hello, not sure if it's a bug or just I'm not doing it right
I'm generating / obfuscating 2 different js files that are both loaded in the same script/page
options_browser.sourceMap = true; options_browser.sourceMapMode = "inline";I can only see one of the two sourcemaps in DevTools, the one is labeled as "sourceMap"
If i manually delete the inline sourcemap (the one I see in devtools) and refresh the page, then I see the other one, labeled aswell as "sourceMap".
At this point, the only thing I can guess is that they are called the same internally and one is overwriting the other.
I have researched a bit about
inputFileNamebut this only works if thesourceMapSourcesModeoption has the valuesources.(this option does not include inline sourcemap content)As per DevTools AI , Google Chrome seems to support differents inline sourcemaps:
Chrome DevTools fully supports multiple files, each containing its own inline source map. This is a standard and widely used method for development.Any thoughts?
All reactions