#Create command

Bootstrap a new browser extension project from an official template in one command.

create scaffolds files, config, and starter scripts for the selected template and optionally installs dependencies.

#When to use create

• Start a new extension from scratch.
• Spin up multiple proof-of-concept ideas quickly.
• Standardize onboarding for teammates with consistent template defaults.

#Create command capabilities

#Usage

npx extension@latest create <extension-name|extension-path> [options]

pnpx extension@latest create <extension-name|extension-path> [options]

yarn dlx extension@latest create <extension-name|extension-path> [options]

#Command options

#Shared global options

Also supports global flags.

#Example commands

npx extension@latest create my-extension --template=new-react

pnpx extension@latest create my-extension --template=new-react

yarn dlx extension@latest create my-extension --template=new-react

npx extension@latest create my-extension --template=init --install=false

pnpx extension@latest create my-extension --template=init --install=false

yarn dlx extension@latest create my-extension --template=init --install=false

#Available templates

React

Build polished extension interfaces with React, strong tooling, and a mature component ecosystem.

Open template

Preact

Get a React-like workflow with a lighter runtime and smaller bundles.

Open template

Vue

Use single-file components and clear conventions for maintainable extension UIs.

Open template

Svelte

Ship interactive UIs with concise components and minimal runtime overhead.

Open template

TypeScript

Add type safety for clearer refactors and long-term maintainability.

Open template

JavaScript

Start fast and ship quickly with the lightest setup, while keeping the path clear for rapid prototypes, production-ready features, and teams that want minimal ceremony.

Open template

#Best practices

• Start from a template that matches your UI/runtime needs to reduce setup drift.
• Keep the first run small, then add extra tooling after verifying baseline command flow.

#Next steps

• Develop your extension with dev.
• Validate production behavior with start.
• Configure shared defaults in extension.config.js.