
Comparing tools? See how Extension.js compares to other frameworks in the
framework comparison.
CLI version: Run
extension --version (or npx extension@latest --version) for the build you are using. The extension package on
npm lists the latest publish.
GitHub releases track
changelog-style notes without tying these docs to a specific patch number.Video walkthrough
Choose your path
Choose the right command
Start a new extension
create command to scaffold a new project and --template to start from a stack-specific baseline.
Use Extension.js with an existing extension
extension package and wire scripts once. This keeps local development, testing, and release builds consistent.
Step 1: install the extension package as a devDependency
Step 2: link your npm scripts to the extension commands
package.json
- Run
npm run devfor daily iteration and watch mode. - Run
npm run startfor production build + immediate launch. - Run
npm run buildfor store-ready production artifacts.
Best practices
- Keep one command flow: Use
create→dev→buildas your default loop. - Target browsers explicitly: Validate with
--browser=chrome,firefoxbefore release. - Centralize defaults: Put shared command/browser settings in
extension.config.js.
Next steps
Create your first extension
Guided walkthrough for your first build.
Templates
Browse starter templates for every stack.
Playwright E2E
Add quality gates to your workflow.
Telemetry and privacy
Review the privacy contract.
Compare frameworks
How Extension.js compares to other browser extension frameworks.

