unjs/unplugin

Unified plugin system for Vite, Rollup, Webpack, esbuild, Rolldown, and more

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 26 seconds ago
Added to GitGenius on September 19th, 2026
Created on July 12th, 2021
Open Issues & Pull Requests: 43 (+0)
GitHub issues: Enabled
Number of forks: 156
Total Stargazers: 3,612 (+1)
Total Subscribers: 13 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.3 hours
Mean response time: 120.0 days
90th percentile: 409.5 days
Tracked items: 43

Most active contributors

Sign in to see contributor activity.

How this project is maintained

85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 91% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 20
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 760 days
Stale 30+ days: 19
Stale 90+ days: 19

Recent activity

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

Top labels

  • bug (22)
  • enhancement (14)
  • documentation (3)
  • pr welcome (2)
  • webpack (2)
  • help wanted (1)
  • rspack (1)
  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Unplugin is a unified plugin system that enables developers to write a single plugin implementation that works across Vite, Rollup, Webpack, esbuild, Rspack, Rsbuild, Rolldown, Farm, Bun, and frameworks built on top of them.

The problem unplugin solves is plugin fragmentation across the JavaScript build tool ecosystem. Each build tool has its own plugin API, forcing plugin authors to maintain separate implementations or users to choose tools based on plugin availability. Unplugin provides a unified abstraction layer that translates a single plugin definition into compatible implementations for all supported build tools, eliminating the need for tool-specific rewrites.

Plugin authors should choose unplugin when they want to maximize compatibility across the modern build tool landscape without maintaining multiple codebases. It suits projects that aim to provide tooling that works regardless of which build system users have adopted. Teams building framework-agnostic utilities, code transformers, or development tools benefit most from this approach, as it removes the barrier of tool-specific plugin development.

The project maintains active development with regular updates to support newly emerging build tools and maintain compatibility as existing tools evolve. The codebase receives consistent refinement to improve the abstraction layer and expand the range of supported build systems. Documentation is actively maintained to reflect current capabilities and guide plugin authors through implementation patterns.