wxt-dev/queue — explained in plain English
Analysis updated 2026-07-31 · repo last pushed 2026-04-30
Fetch details about your browser extensions from multiple stores through a single API.
Inspect what data the API returns for extensions listed on different store platforms.
Track and coordinate extension release updates across Chrome, Firefox, and Edge once queuing is built.
| wxt-dev/queue | 1000sbin/moa-goods-maker | brunosimon/esin-e1-p2026 | |
|---|---|---|---|
| Stars | 11 | 11 | 11 |
| Language | HTML | HTML | HTML |
| Last pushed | 2026-04-30 | — | 2022-05-15 |
| Maintenance | Maintained | — | Dormant |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 1/5 | 1/5 |
| Audience | developer | general | general |
Figures from each repo's GitHub metadata at analysis time.
Requires running a local dev server and comfort exploring API endpoints without full documentation.
wxt-queue is an early-stage project meant to help developers manage browser extensions across multiple stores. The core idea is a service that lines up extension updates waiting for review, so you can push releases in an organized queue rather than juggling them manually across platforms like the Chrome Web Store or Firefox Add-ons. Right now, though, it's still a work in progress and only provides an API for fetching extension details from various stores. At a high level, the project runs a small server you start locally during development. Once running, it gives you an API endpoint to query for information about extensions listed in different browser extension stores. The README mentions that it generates GraphQL types automatically based on a schema while the server runs, and it exposes OpenAPI documentation through a link shown in the console. Beyond that, the README doesn't go into much detail about which stores are supported or how the queueing system will eventually work. The people who'd find this useful are developers who maintain browser extensions and publish updates across more than one store. If you've ever tried to coordinate a release across Chrome, Firefox, and Edge, you know each store has its own review timeline and quirks. A tool that pulls extension details into one place, and eventually manages release queues, would save time and reduce the chance of missing a store or shipping out of sync. The current API-only state means it's best suited for someone comfortable poking around an endpoint to see what data comes back, rather than someone expecting a finished product. What stands out is how early and minimal the project is right now. The README is essentially a quickstart with install and dev commands, and the description tags it as "WIP." That signals the project is still finding its shape, and the full CI/CD vision for queuing store releases isn't built yet. The tradeoff is straightforward: you get a lightweight starting point with modern tooling, but you're looking at the foundation of something rather than a complete tool.
A work-in-progress service that gives developers an API to fetch browser extension details from multiple stores, with plans to eventually queue and coordinate extension release updates across platforms.
Mainly HTML. The stack also includes HTML, GraphQL, OpenAPI.
Maintained — commit in last 6 months (last push 2026-04-30).
No license information is provided in the README, so usage rights are unclear.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.