crxjs/chrome-extension-tools

Build cross-browser extensions with native HMR and zero-config setup

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 16th, 2026
Created on March 15th, 2019
Open Issues & Pull Requests: 24 (+0)
GitHub issues: Enabled
Number of forks: 246
Total Stargazers: 4,170 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 42.5 hours
Mean response time: 43.1 days
90th percentile: 104.1 days
Tracked items: 188

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 17% of issues opened in the past year have never received a reply. Work labelled "enhancement" is answered fastest, typically in about 3 days, while "not-stale" waits about 7 weeks. 73% of issues opened in the past year have been closed, leaving a working backlog. Three people close 78% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 0
Closed in 7 days: 4
Avg open age: 330 days
Stale 30+ days: 14
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 2

Top labels

  • Stale (124)
  • enhancement (46)
  • vue (22)
  • bug (16)
  • not-stale (12)
  • vite-plugin (9)
  • docs (7)
  • windows (6)

Detailed Description

CRXJS is a Vite plugin and Rollup plugin that streamlines building Chrome and cross-browser extensions with hot module replacement and minimal configuration.

The tool addresses the friction of extension development by providing native HMR support and zero-config setup, eliminating boilerplate typically required when building browser extensions. It works as a plugin integrated into Vite or Rollup, handling the complexity of extension bundling and manifest management automatically while developers write their extension code using standard web development workflows.

Developers building Chrome extensions or cross-browser extensions should adopt this tool if they want to leverage modern tooling like Vite without wrestling with extension-specific build configuration. It suits projects targeting Manifest V2 and Manifest V3, allowing teams to use the same development experience they would have with standard web applications. The tool is particularly valuable for teams already invested in Vite or Rollup ecosystems who want to extend that workflow to extension development.

The project maintains active development with regular updates addressing both new features and bug fixes. The codebase shows consistent attention to supporting both Vite and Rollup as first-class build targets, with plugin implementations for each. Documentation is actively maintained through the project website, indicating ongoing investment in developer experience and onboarding.