WebExt Deploy

The ultimate automation tool for deploying to multiple extension stores simultaneously!

Made by Avi

Supported stores:

• Chrome Web Store
  • .env snippet
  • CLI API
• Firefox Add-ons
  • .env snippet
  • CLI API
• Edge Add-ons
  • .env snippet
  • CLI API
• Opera Add-ons
  • .env snippet
  • CLI API

Core packages/APIs used

• Playwright - for fetching Opera credentials
• Chrome Web Store API v2
• Microsoft Edge Publish API v1.1
• Firefox Add-ons Store Submission API
• Opera Store API

Installing

npm i -D web-ext-deploy
# or
pnpm i -D web-ext-deploy
# or
bun add -D web-ext-deploy

or install globally

npm i -g web-ext-deploy
# or
pnpm i -g web-ext-deploy
# or
bun add -g web-ext-deploy

Deployment to Chrome Web Store: follow this guide
Deployment to Edge Add-ons Store: follow this guide

Usage

1. Get the relevant credentials for each store:

Disclaimer: I do NOT take any responsibility for leaked cookies or credentials.

• Opera: sessionid, csrftoken — obtained via Playwright (use --auto-fetch-credentials to fetch automatically)
• Chrome: REFRESH_TOKEN — obtained via OAuth (use --auto-fetch-credentials to fetch automatically)

For the Edge Add-ons Store, you'll use the Microsoft Edge Publish API

2. Decide how to access the data & credentials

• .env files method
• CLI arguments method

.env files method

Use the .env snippet(s) relevant to your extension
Include each one in your root directory
Make sure to have *.env or chrome.env, firefox.env, edge.env, opera.env in your .gitignore

Next, in the CLI:

web-ext-deploy env

Options for env mode

Global:

Chrome overrides:

Firefox overrides:

Edge overrides:

Opera overrides:

Notes:

• Chrome Web Store:

  • REFRESH_TOKEN - follow this guide, or omit and run web-ext-deploy env --auto-fetch-credentials to fetch and save it automatically
  • PUBLISHER_ID - Get it from the Chrome Web Store Developer Dashboard > Account
  • EXT_ID - Get it from https://chromewebstore.google.com/detail/EXT_ID

• Firefox Add-ons store:

  • EXT_ID - Get it from https://addons.mozilla.org/addon/EXT_ID
  • ZIP - The relative path to the ZIP. You can use {version}, which will be replaced by the version entry from your package.json
  • ZIP_SOURCE - Optional. The relative path to the ZIP that contains the source code of your extension, if applicable
  • JWT_ISSUER, JWT_SECRET - obtain from the Developer Hub

• Edge Add-ons store:

  • CLIENT_ID, API_KEY - follow this guide
  • PRODUCT_ID - Get it from https://partner.microsoft.com/en-us/dashboard/microsoftedge/PRODUCT_ID
  • ZIP - You can use {version}

• Opera Add-ons store:

  • PACKAGE_ID - Get it from https://addons.opera.com/developer/package/PACKAGE_ID
  • ZIP - You can use {version}
  • SESSIONID, CSRFTOKEN - can be omitted if you run web-ext-deploy env --auto-fetch-credentials (fetches and saves them automatically via Playwright)
  • Source code inspection:
    The Opera Add-ons reviewers require inspecting your extension's source code
    This can be done by doing one of the following:
    • Uploading the ZIP that contains the source code to a public folder on a storage service (e.g. Google Drive)
    • Making the extension's code open source on a platform like GitHub, with clear instructions on the README.md, and then linking to its repository

• The keys are case-insensitive, as they will be camel-cased anyway

Possible .env files

chrome.env

EXT_ID="ExtensionID"
PUBLISHER_ID="PublisherID"
REFRESH_TOKEN="RefreshToken"
ZIP="dist/some-zip-v{version}.zip"

firefox.env

JWT_ISSUER="JwtIssuer"
JWT_SECRET="JwtSecret"
ZIP="dist/some-zip-v{version}.zip"
ZIP_SOURCE="dist/some-zip-source-v{version}.zip"
EXT_ID="ExtensionID"
CHANGELOG_LANG="en-US"

edge.env

CLIENT_ID="ClientID"
API_KEY="ApiKey"
ZIP="dist/some-zip-v{version}.zip"
PRODUCT_ID="ProductID"

opera.env

SESSIONID="sessionid_value"
CSRFTOKEN="csrftoken_value"
ZIP="dist/some-zip-v{version}.zip"
PACKAGE_ID=123456

CLI arguments method

Use it only if your extension's code will not be publicly available

web-ext-deploy cli --chrome-zip="some-zip-v{version}.zip" --chrome-ext-id="ExtensionID" --firefox-zip="some-zip-v{version}.zip" --firefox-ext-id="ExtensionID"

CLI API

Stores:

• Chrome Web Store
• Firefox Add-ons
• Edge Add-ons
• Opera Add-ons

Options:

Chrome Web Store CLI

Example:

web-ext-deploy cli --chrome-ext-id="ExtensionID" --chrome-publisher-id="PublisherID" --chrome-refresh-token="RefreshToken" --chrome-zip="some-zip-v{version}.zip"

Or, fetch the refresh token automatically (opens a browser for OAuth consent):

web-ext-deploy cli --auto-fetch-credentials --chrome-ext-id="ExtensionID" --chrome-publisher-id="PublisherID" --chrome-client-id="ClientID" --chrome-client-secret="ClientSecret" --chrome-zip="some-zip-v{version}.zip"

Firefox Add-ons CLI

Example:

web-ext-deploy cli --firefox-ext-id="ExtensionID" --firefox-jwt-issuer="JwtIssuer" --firefox-jwt-secret="JwtSecret" --firefox-zip="dist/some-zip-v{version}.zip"

Edge Add-ons CLI

Example:

web-ext-deploy cli --edge-product-id="ProductID" --edge-client-id="clientId" --edge-api-key="apiKey" --edge-zip="dist/some-zip-v{version}.zip"

Note:
Due to the way the Edge dashboard works, when an extension is being reviewed or its review has just been canceled, it will take about a minute until a cancellation will cause its state to change from "In review" to "In draft", after which the new version can be submitted
Therefore, if you publish after you had just published/canceled, expect to wait a little longer

Opera Add-ons CLI

Example:

web-ext-deploy cli --opera-package-id=123456 --opera-sessionid="sessionid_value" --opera-csrftoken="csrftoken_value" --opera-zip="dist/some-zip-v{version}.zip"

Or, fetch the cookies automatically via Playwright:

web-ext-deploy cli --auto-fetch-credentials --opera-package-id=123456 --opera-zip="dist/some-zip-v{version}.zip"

Notes:

• Source code inspection:
  The Opera Add-ons reviewers require inspecting your extension's source code.
  This can be done by doing one of the following:

  • Uploading the ZIP that contains the source code to a public folder on a storage service like Google Drive
  • Making the extension's code open source on a platform like GitHub, with clear instructions on the README.md, and then linking to its repository.

  Note that you do not want to store the command with your extension package, as the review team will have access to your credentials.