Firefox Add-on review process is wrong and Firefox is a lost cause. Im out

[freaktechnik (Martin Giger)]

@tmarois

Here’s the catch. From my understanding, the source is there so they can read the code if need be. Otherwise, I don’t see what else you would need a source for. You want to check it for security, see what exactly is going out without obscuring the code.

As this person at Mozilla builds from the source,

Yes, how else would you verify that the provided source actually generates the extension you submitted? If the source doesn’t represent what you submitted, it can’t be used to check what the extension does…

they complain that the files aren’t the same. No shit. You built them locally on your machine, on your OS, on your node. As some of you know, frameworks like Nuxt generate random file names, and with webpack, the code base can never be compared because of how it chunks.

I’m not familiar enough with nuxt, but I do know that webpack can be configured to create a reproducible build, where the filenames and contents are deterministic from the input files.