Our take
Archivedarchived by its owners on GitHub, read-only- Activity
- 19
- Community
- 72
- Issues
- 21
- Pull requests
- 20
-10 stars in the last 30 days
This is a feature-rich extension starter, but its archived, read-only status makes it a poor choice as the foundation for a project that needs ongoing upstream maintenance.
Good fit if
- You want to study or adapt an existing React, TypeScript, and Vite extension structure.
- Your team can maintain the boilerplate itself and needs its modular pages, custom HMR, or packaging tools.
- You are comfortable with the MIT license and can meet its Node.js version requirement.
Look elsewhere if
- You need an actively maintained starter or expect upstream fixes and releases.
- You need a project with recent issue or pull-request handling, which the available health data does not show.
- Your environment cannot use Node.js 22.15.1 or newer.
All health signals
| Last commit | 2025-10-27 (12 months ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 (latest 0.5.2, 2025-07-18) |
| Contributors | 52 (top contributor: 42% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 4 years |
Checked on 2026-10-11 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
4,896Forks
663Change since Nov 13, 2026: -1 stars·-1 forks
Overview
This repository is a React and TypeScript boilerplate for Chrome and Firefox extensions. It combines Vite and Turborepo to organize extension pages and shared packages, aiming to make extension development and builds easier to manage.
It is a starting point rather than a finished extension. Teams can adapt its example modules, manifest, and shared tooling to their own browser-extension projects.
Key Features
- Builds extensions for Chrome and Firefox using Vite and Rollup.
- Includes React, TypeScript, and Tailwind CSS support.
- Organizes extension surfaces such as popups, options pages, new tabs, side panels, and DevTools panels.
- Provides a custom hot-module-reload plugin for development.
- Includes shared packages for storage, internationalization, environment variables, and configuration.
- Supports extension packaging and end-to-end testing with WebdriverIO.
- Uses Chrome Manifest Version 3 and includes a module manager for enabling or disabling modules.
Use Cases
- A frontend developer starting a React-based Chrome or Firefox extension who wants a working project structure and build setup.
- An extension team that needs several interfaces, such as a popup, options page, and content UI, organized in one repository.
- A team building an extension with shared localization or storage helpers and wanting those concerns separated into packages.
- Developers who want to run browser-specific builds and test a packaged extension as part of their development workflow.
What you need
Detected in the repository
- Node.js >=22.15.1 (from package.json)
- A test suite and automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Clone the repository, then install dependencies:
pnpm install
For browser-specific development and build commands, see the README.
Alternatives
- extension.js: A cross-browser framework and CLI for building extensions, rather than a React-and-Vite starter with a fixed project setup.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| chrome-extension-boilerplate-react-vite | TypeScript | MIT | 4.9k | Archived |
| extension.js | TypeScript | MIT | 5.2k | Active |
Considerations
The repository is archived and read-only. It has had no commits in the recent 90-day period, no releases in the past year, and no issues closed or pull requests merged in that period. It has 52 contributors, and the measured contribution share does not indicate that work is concentrated on one person, but archived status still means fixes and compatibility updates are not expected from the maintainers.
The README says Windows users should use WSL and notes that development is configured with broad access to data on all websites, which should be narrowed to the permissions an extension actually needs before production. Firefox add-ons loaded through the documented development flow are temporary and must be loaded again after the browser closes. The project requires Node.js 22.15.1 or newer.
Found this useful?
Share it with someone who would like chrome-extension-boilerplate-react-vite.