> ## 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.

# Extension.js roadmap

> Track Extension.js releases, milestones, and roadmap discussions. See what is shipping now, what is next, and what is planned for the framework.

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.

## Where to track work

| Surface                                                                        | What it tells you                                                              |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ |
| [GitHub Releases](https://github.com/extension-js/extension.js/releases)       | Every published version with notes. The source of truth for what shipped when. |
| [GitHub Milestones](https://github.com/extension-js/extension.js/milestones)   | Issues grouped by upcoming version. Best signal for what is queued next.       |
| [GitHub Discussions](https://github.com/extension-js/extension.js/discussions) | Proposals, RFCs, and longer-form direction setting.                            |
| [Open issues](https://github.com/extension-js/extension.js/issues)             | Active bugs and feature requests.                                              |
| [Discord](https://discord.gg/v9h2RgeTSN)                                       | Day-to-day coordination, questions, and informal previews.                     |
| [npm package page](https://www.npmjs.com/package/extension)                    | 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.

Pin to a specific version in your `devDependencies` or use `extension@latest` for the most recent publish. The [npm package](https://www.npmjs.com/package/extension) page lists every version.

## Asking for something new

If you want a feature that does not exist yet:

1. Search [open issues](https://github.com/extension-js/extension.js/issues) and [discussions](https://github.com/extension-js/extension.js/discussions). Someone may already be tracking it.
2. If not, open a discussion describing the use case before filing an issue. Use cases get prioritized; abstract requests rarely do.
3. 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](/blog) and the [latest release entry on GitHub](https://github.com/extension-js/extension.js/releases). 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](https://github.com/extension-js/extension.js/blob/main/CONTRIBUTING.md) is the entry point. Most issues marked `good first issue` are scoped for first-time contributors.