Publish an extension to all the extension stores in a single command!
\n\nhttps://github.com/aklinker1/publish-browser-extension/assets/10101283/b0e856ca-4e26-4c7e-9ff8-c900e203cab5\n\n## Features\n\n- Publish to the following stores:\n - [Chrome](https://developer.chrome.com/docs/webstore)\n - [Edge](https://microsoftedge.microsoft.com/addons/Microsoft-Edge-Extensions-Home)\n - [Firefox](https://addons.mozilla.org/en-US/firefox/extensions/)\n - [Opera](https://addons.opera.com/developer/)\n\n- Helper script to generate secrets and configure options\n- **Upload sources ZIP** to the Firefox Addon Store\n\n> [!IMPORTANT]\n>\n> You are responsible for uploading and submitting an extension for the first time by hand. `publish-browser-extension` does not provide tools for creating a new extension.\n\n## Install\n\n```sh\nnpm i -D publish-browser-extension\npnpm i -D publish-browser-extension\nbun i -D publish-browser-extension\n```\n\n## CLI Usage\n\nTo get started, run the init command. It will walk you through generating all the necessary environment variables/CLI flags, saving them to a `.env.submit` file:\n\n```sh\npublish-extension init\n```\n\n> All CLI flags can be passed as environment variables instead. For example, setting the `CHROME_CLIENT_ID` environment variable is equivalent to passing `--chrome-client-id`. Just convert the flag to UPPER_SNAKE_CASE.\n\nThen, just run the submit command, passing the ZIP files you want to submit:\n\n```sh\npublish-extension \\\n --chrome-zip dist/chrome.zip \\\n --firefox-zip dist/firefox.zip --firefox-sources-zip dist/sources.zip \\\n --edge-zip dist/chrome.zip \\\n --opera-zip dist/opera.zip\n```\n\n`publish-extension` will automatically look for a `.env.submit` file and load it if it exists.\n\n## JS Usage\n\n```js\nimport { publishExtension } from 'publish-browser-extension';\n\nconst results = await publishExtension({\n // ...\n});\nconsole.log(results);\n```\n\n## Options\n\nRefer to the [Config Reference](./docs/config-reference.md).\n\n## Contributing\n\n\n