Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/aklinker1/publish-browser-extension
CI tool to easily publish browser extensions
https://github.com/aklinker1/publish-browser-extension
chrome-extension chrome-web-store web-extension
Last synced: 14 days ago
JSON representation
CI tool to easily publish browser extensions
- Host: GitHub
- URL: https://github.com/aklinker1/publish-browser-extension
- Owner: aklinker1
- License: mit
- Created: 2022-05-30T13:21:31.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-09-20T18:45:32.000Z (about 2 months ago)
- Last Synced: 2024-09-21T10:09:01.071Z (about 2 months ago)
- Topics: chrome-extension, chrome-web-store, web-extension
- Language: TypeScript
- Homepage:
- Size: 1020 KB
- Stars: 46
- Watchers: 1
- Forks: 4
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
Publish Browser Extension
Publish an extension to all the extension stores in a single command!
https://github.com/aklinker1/publish-browser-extension/assets/10101283/b0e856ca-4e26-4c7e-9ff8-c900e203cab5
## Features
- Publish to the **Chrome Web Store**, **Firefox Addon Store**, and **Edge Addon Store**
- Helper script to generate secrets and configure options
- **Upload sources ZIP** to the Firefox Addon Store
> [!IMPORTANT]
>
> 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.
## Install
```sh
npm i -D publish-browser-extension
pnpm i -D publish-browser-extension
yarn add -D publish-browser-extension
```
## CLI Usage
To 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:
```sh
publish-extension init
```
> 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.
Then, just run the submit command, passing the ZIP files you want to submit:
```sh
publish-extension \
--chrome-zip dist/chrome.zip \
--firefox-zip dist/firefox.zip --firefox-sources-zip dist/sources.zip \
--edge-zip dist/chrome.zip
```
`publish-extesion` will automatically look for a `.env.submit` file and load it if it exists.
## JS Usage
```js
import { publishExtension } from 'publish-browser-extension';
publishExtension({
dryRun: true,
chrome: {
zip: 'dist/chrome.zip',
extensionId: '',
clientId: '',
clientSecret: '',
refreshToken: '',
publishTarget: '',
skipSubmitReview: false,
},
firefox: {
zip: 'dist/firefox.zip',
sourcesZip: 'dist/sources.zip',
extensionId: '',
jwtIssuer: '',
jwtSecret: '',
channel: '',
},
edge: {
zip: 'dist/chrome.zip',
productId: "",
clientId: "",
clientSecret: "",
accessTokenUrl: "",
skipSubmitReview: false,
},
})
.then(results => console.log(results))
.catch(err => console.error(err));
```
## Contributing
### Contributor Setup
1. Install [node](https://nodejs.org)
2. Install [`pnpm`](https://pnpm.io/)
```sh
corepack enable
```
3. Install dependencies
```sh
pnpm i
```
4. Run the `init` command to generate a `.env.submit` file for testing
```sh
pnpm publish-extension init
```
> [!WARNING]
>
> Make sure to set the Firefox channel to "unlisted", chrome's publish target to "trustedTesters", and don't submit the extension for review for Chrome or Edge. This will prevent you from accidentally releasing one of the test extensions publically.
5. Run the dev commands to upload a test extension to the stores:
```sh
pnpm dev:all
pnpm dev:chrome
pnpm dev:firefox
pnpm dev:edge
```