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
| Capability | What it gives you |
|---|---|
| Template scaffolding | Start from official templates with ready project structure |
| Dependency bootstrap | Install required packages automatically after scaffold |
| Path flexibility | Create by project name or explicit folder path |
| Fast onboarding | Move from empty folder to runnable extension quickly |
Usage
Command options
| Flag | Alias | What it does | Default |
|---|---|---|---|
[path or name] |
- | Project directory/name to create. | required |
--template <name> |
-t |
Selects template slug. | default |
--install [boolean] |
- | Installs dependencies after scaffolding. | true |
Shared global options
Also supports global flags.
Example commands
Available templates
React
Mature React ecosystem with reusable components, strong tooling, and scalable patterns for production extension interfaces.
Open template
Preact
React-like developer experience with lighter runtime, faster startup, and smaller bundles for performance-sensitive extensions teams.
Open template
Vue
Single-file component workflow with clear conventions, rich ecosystem plugins, and maintainable architecture for browser extensions.
Open template
Svelte
Compiler-first approach delivering concise components, minimal runtime overhead, and excellent performance for interactive extension UIs.
Open template
TypeScript
Type-safe foundation that improves refactoring confidence, collaboration clarity, and long-term maintainability across extension codebases.
Open template
JavaScript
Fastest setup for rapid prototyping, quick iteration, and shipping functional extensions without upfront type-system complexity.
Open templateBest 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.