Skip to main content
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

​
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 page lists every version.

​
Asking for something new

If you want a feature that does not exist yet:
  1. Search open issues and 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 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 marked good first issue are scoped for first-time contributors.