![]() Firefox main release schedule is the master location for the dates when each Firefox version goes to Aurora, Beta, & Release.Īs we plan what's coming next, we're focused on the themes outlined here.Bi-Weekly Team Meeting: time and date TBD.Something here about what Team AddOns is responsible for with links to other key AddOns assets 1.1 Meetings, Status Reports, Communications.This runs Prettier on only your changed files. This runs Prettier to automatically format the entire codebase. ESLint also enforces some patterns and practices. This runs ESLint to discover problems within our codebase without executing it. See the Writing commit messages section for more information. See the Releasing section for more information. This creates a changelog of all unreleased changes (in markdown). ![]() This packages the library for production into the dist/ folder. There are a few commands not mentioned here (see package.json) but those are only used by internal processes. In the project directory, you can run the following commands. As a developer, you have to run it (with npm run prettier-dev) before submitting a Pull Request. We use Prettier to automatically format our JavaScript code and stop all the on-going debates over styles. Install all requirements and run tests from the source: Here's how to set up a development environment for the sign-addon package. You must pass id to signAddon() for all other non-WebExtension add-ons.To push an updated version to a WebExtension that had its ID auto-generated, you need to pass in the original ID explicitly.If a WebExtension's manifest.json already declares an ID, any id you pass to signAddon() will have no effect!.In this case, an ID will be auto-generated for you. WebExtensions do not require you to pass id to signAddon().Here are some notes about dealing with IDs when using signAddon():
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |