Automates the publishing of web extensions to Chrome, Firefox, and Opera stores via CLI.
Web Extensions - Shipit is a Node.js CLI tool that automates the process of publishing browser extensions to official stores like Chrome WebStore, Mozilla Add-ons, and Opera Extensions. It handles credential management and submission steps, turning a manual, error-prone process into a single command.
Web extension developers and teams who regularly update and publish extensions across multiple browser platforms and want to automate their deployment pipeline.
It saves significant time and reduces human error by automating store submissions, supports multiple browsers from one tool, and integrates easily into existing CI/CD workflows with environment-based configuration.
Automate the process of shipping Web Extensions for Chrome, Firefox, Safari, Opera and Edge
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports Chrome, Firefox, and Opera from a single CLI tool, automating uploads and submissions as shown in the usage examples with commands like `shipit chrome <folder>`.
Uses environment variables or a .env file to handle store credentials securely, preventing accidental exposure in version control, as recommended in the README's credentials section.
Offers straightforward commands such as `shipit firefox distribution/firefox-prod`, making it easy to integrate into build scripts or CI/CD pipelines.
Automates the entire submission process to browser stores, saving time and minimizing human error compared to manual uploads and form submissions.
Does not support Safari or Edge extensions, as indicated by the ❌ in the implementation table, limiting its utility for projects targeting all major browsers.
Requires following external guides to generate API keys and tokens for each browser store, such as Chrome's WebStore API or Firefox's JWT credentials, which can be tedious and error-prone.
The README is concise and may not cover advanced use cases or troubleshooting, relying on community contributions with 'PRs welcome', suggesting some features are missing or immature.