CLI tool to upload and publish Chrome extensions to the Chrome Web Store from the command line.
chrome-webstore-upload-cli is a command-line tool that allows developers to upload and publish Chrome extensions to the Chrome Web Store programmatically. It wraps the Web Store Upload module to provide a CLI interface, solving the problem of manual extension deployment by enabling automation through scripts and CI/CD pipelines.
Chrome extension developers and teams who need to automate the deployment process, integrate with CI/CD systems like GitHub Actions, or manage extensions via command-line workflows.
Developers choose this tool because it eliminates manual Web Store interactions, provides a reliable and scriptable way to deploy extensions, and integrates seamlessly with existing development and automation workflows.
CLI tool to upload Chrome Extensions to the Chrome Web Store
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built specifically for CI/CD pipelines, with examples for GitHub Actions and environment variable support, enabling seamless integration into automated release workflows.
Accepts various source formats including zip files, crx files, or directories, and defaults to package.json configuration, simplifying deployment from different project structures.
Uses OAuth2 credentials (client ID, client secret, refresh token) managed via environment variables, ensuring secure access to the Chrome Web Store API without hardcoding secrets.
Provides straightforward commands for upload and publish, with options like trusted testers and deploy percentage, making it easy to script and control releases from the terminal.
Requires obtaining and managing Google API OAuth2 credentials through a multi-step process, which can be time-consuming and confusing for users new to the Chrome Web Store API.
Exclusively designed for the Chrome Web Store; automating deployments for other browsers like Firefox requires separate tools or custom integration, limiting its utility for cross-browser extensions.
The README covers basic usage but lacks detailed examples for error handling, retry logic, or complex deployment scenarios, potentially requiring users to delve into the source code for troubleshooting.