Source maps don't work by default about browser-extension-template HOT 4 CLOSED

@fregante commented on April 11, 2022 1:03 AM:

Thanks for the research. Yeah that's a Chrome limitation. Can you send a PR? The only change is that I'd just name them development and default, the latter is picked up automatically.

Sent - thanks for waiting patiently :-)

from browser-extension-template.

@aspiers commented on April 10, 2022 8:16 PM:

Source maps don't work unless inlined in web extensions

It doesn't explain why they don't work unless inlined, so I'm guessing it's a fundamental browser thing, e.g. a security restriction on extensions.

Did a bit more digging, and found:

• https://stackoverflow.com/questions/61462586/can-i-enable-sourcemaps-in-a-chrome-extension/62270410#62270410
• https://bugs.chromium.org/p/chromium/issues/detail?id=212374
• https://bugs.chromium.org/p/chromium/issues/detail?id=974543

so it seems this issue has been going on since 2013 in Chromium and derivatives, and is perhaps very recently fixed, or close to being fixed.

from browser-extension-template.

Thanks for the research. Yeah that's a Chrome limitation. Can you send a PR? The only change is that I'd just name them development and default, the latter is picked up automatically.

from browser-extension-template.

This has likely been fixed in the meanwhile:

• #87

This is what I see now:

Unless I manually disable the source maps:

from browser-extension-template.