webpack/tapable

Just a little module for plugins.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 17th, 2026
Created on January 21st, 2013
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 390
Total Stargazers: 3,861 (+0)
Total Subscribers: 44 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.9 days
Mean response time: 311.2 days
90th percentile: 1364.2 days
Tracked items: 19

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,133 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Tapable is a plugin system library that provides a foundation for building extensible applications through hooks.

The tool solves the problem of enabling plugins to tap into and modify application behavior at specific points in execution. It works by exposing a set of hook types—including synchronous, asynchronous, waterfall, and bail hooks—that allow plugins to register callbacks at predefined stages. Each hook type enforces different execution semantics: some run all registered callbacks in sequence, others stop at the first callback that returns a value, and others pass return values through a chain of transformations. This design lets application authors define extension points without needing to implement custom plugin infrastructure.

Tapable suits projects that need a lightweight, standardized way to support plugins without heavy dependencies. It works well for build tools, bundlers, and other systems where multiple independent pieces of code need to hook into core processes. The library is minimal by design, making it appropriate when you want plugin capabilities without framework overhead. Developers should choose it if their application architecture already involves multiple stages of processing where plugins naturally fit, rather than retrofitting it into monolithic designs.

The project maintains a stable, focused codebase with minimal churn. Commits are sparse and deliberate, reflecting a mature tool that has settled into its design. Pull requests are infrequent and typically address specific issues rather than driving continuous feature expansion. The project does not show signs of active development velocity, but this aligns with its role as a foundational utility that has reached a stable state. Issue activity is low, suggesting either that the tool is well-understood and meets its users' needs or that it has a small active user base. The sparse activity pattern indicates the maintainers treat this as a stable dependency rather than a project requiring ongoing evolution.