broccolijs/broccoli

Browser compilation library – an asset pipeline for applications that run in the browser

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 20th, 2026
Created on May 14th, 2013
Open Issues & Pull Requests: 36 (+0)
GitHub issues: Enabled
Number of forks: 204
Total Stargazers: 3,322 (+0)
Total Subscribers: 62 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 148.8 days
Mean response time: 228.1 days
90th percentile: 567.1 days
Tracked items: 5

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

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

Sign in to see which issues are moving.
Sign in

Detailed Description

Broccoli is an asset pipeline for browser applications that compiles and transforms source files into optimized browser-ready output.

The tool solves the problem of managing complex build workflows for web applications by providing a declarative, composable system for defining asset transformations. It works by allowing developers to construct a tree of build operations where each step takes input files, applies transformations, and produces output that feeds into the next stage. This functional approach makes build pipelines explicit and testable, with each transformation clearly defined as a discrete operation in the chain.

Broccoli suits projects that need fine-grained control over their build process and benefit from a transparent, composable architecture. It works well for applications where understanding exactly what happens at each build stage matters, and where the ability to reuse and combine build operations across projects is valuable. The tool is particularly useful for teams building complex single-page applications or libraries that require sophisticated asset handling beyond simple bundling.

The project maintains active engagement with its codebase through regular updates and responsive issue management. Development shows consistent attention to both new features and maintenance of existing functionality. The maintainers demonstrate commitment to keeping the tool compatible with evolving JavaScript ecosystems and addressing user-reported problems promptly.