web-ext
web-ext copied to clipboard
mozilla
A command line tool to help build, run, and test web extensions
Looking at the ESLint config as part of #2506, we could probably simplify it (taking inspiration from the other AMO repos like addons-linter). This issue is about refactoring our ESLint...
Background: AMO's submission API has three endpoints for creating a version from an xpi `Upload`: 1. POST to `/addons/addon/` to create a new add-on listing with the new version 2....
Right now the `addon-id` is saved in `.web-extension.id` _after_ the xpi has been downloaded. If the approval check times out, or the user cancels the wait before the timeout, the...
We shouldn't have to think or argue about codestyle so let's use Prettier like in most other projects we maintain.
#2451 added support for signing add-ons via addons.mozilla.org/api/v5/addons/addon/ api endpoints (aka addon submission api), which an experimental `--use-submission-api`. Before it's released (or perhaps publicized, if it's released earlier) there are...
https://addons-server.readthedocs.io/en/latest/topics/api/addons.html supports some fields which are set or updated by uploading a file, as multipart-formdata. The addon `icon`, version `source`, and preview images are all file uploads - they are...
With the submission api the validation is effectively split up into two stages - upload validation, including the linter, scanners, etc, and then the addon/version validation, which is mainly (but...
follow-on from #2451 AMOs addon submission api supports setting a number of add-on properties on add-on and version creation - and strictly requires some of these properties be provided while...
The node stream api doesn't have promise support until [node 15](https://nodejs.org/api/stream.html#streams-promises-api), so it needs to be wrapped in `promisify` under node 14. Once we up our minimum node to 16...