Don't minify extension source code.

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.

Start by locating the extension build configuration and identifying where minification and bundling are applied. Determine how the packaged extension is produced, then verify that the resulting extension remains functional while its source and injected code are readable for debugging.