solution for predictable filenames

[escapewindow]

Currently, web-ext hardcodes the filepath web-ext-artifacts/LOWERCASE_PACKAGE-VERSION.zip. This means that we can't reliably determine what the artifact name will be from xpi-manifest, without downloading all the respective package.json files for each xpi. (This latter approach would be simplified if we used a monorepo, but as of this writing that goes against our current requirements.)

The current workaround is to wrap the web-ext build with a script that renames the artifact afterwards. That's one approach, but it seems unwieldy, since web-ext is a Mozilla project.

The best solution appears to be adding an option to web-ext to specify a filepath or filepath template. I filed mozilla/web-ext#1844 , which was duped to mozilla/web-ext#1335 . There appears to be an abandoned patchset for the latter issue; we can potentially unbitrot it and get it landable.

This is on my todo list back burner for when I have time, but I'm happy for any help here as well.

[escapewindow]

mozilla/web-ext#1900 landed on May 11. I pinged to see if/when we can get a new release of web-ext. Once that happens, we can resolve this.

[escapewindow]

web-ext 4.3.0 supports web-ext build --filename . #33 tracks specifying the artifact name in package.json if we want further customizability. Resolving this issue.