Don't minify extension source code.

[MicahZoltu]

Unlike web pages served over the internet, extensions don't suffer nearly as much from large file sizes since you download the extension once at install time and then never again (aside from occasional automatic background updates). The minification process that the code goes through significantly impacts the ability to debug the extension and the code it injects into the page.

Recommend not minfying the extension and instead shipping it as a largely unbundeld/unminified codebase so that debugging is maximally easy. My guess is that this would increase the extension download size from epsilon to inconsequential, which feels like an acceptable trade off for making it easier for your users to track down bugs in the extension rather than having to create a repro case and then forward it on to you.

[marvinhagemeister]

I'm not sure by that as the extension code isn't minified. It's merely bundled as it's way easier to inject a single file into the page context.

[MicahZoltu]

I don't know why I previously thought this was minified, this GitHub issue did a very poor job of showing the problem as even I can't figure out what I meant now. 😖

That being said, I can see that source maps aren't included, so perhaps we can just convert this issue to "Include source maps".

preact-devtools/tools/build.mjs

Line 111 in 1a42f72

sourcemap: false,

This would make it so debugging is a bit easier as it would be in the language originally written (TS) rather than the transpilation target (JS).