Extension.js development happens in the open. This page tells you where to look for what is shipping, what is queued, and what is being discussed.Documentation Index
Fetch the complete documentation index at: https://extension.js.org/llms.txt
Use this file to discover all available pages before exploring further.
Where to track work
| Surface | What it tells you |
|---|---|
| GitHub Releases | Every published version with notes. The source of truth for what shipped when. |
| GitHub Milestones | Issues grouped by upcoming version. Best signal for what is queued next. |
| GitHub Discussions | Proposals, RFCs, and longer-form direction setting. |
| Open issues | Active bugs and feature requests. |
| Discord | Day-to-day coordination, questions, and informal previews. |
| npm package page | The latest published version. |
How releases work
Extension.js follows semantic versioning:- Patch releases ship bug fixes without behavior changes.
- Minor releases add new flags, capabilities, or template options without breaking existing projects.
- Major releases change defaults or remove deprecated behavior. These come with a migration note in the release entry.
devDependencies or use extension@latest for the most recent publish. The npm package page lists every version.
Asking for something new
If you want a feature that does not exist yet:- Search open issues and discussions. Someone may already be tracking it.
- If not, open a discussion describing the use case before filing an issue. Use cases get prioritized; abstract requests rarely do.
- Tag the discussion with the surface it touches (CLI, manifest, reload, browsers, templates, docs).
Recent direction
For the latest direction, read the most recent post on the blog and the latest release entry on GitHub. The blog covers the why behind major releases; GitHub releases cover the what.Contribute
If a roadmap item interests you and you want to help, the contributing guide is the entry point. Most issues markedgood first issue are scoped for first-time contributors.