brunch/brunch

🍴 Web applications made easy. Since 2011.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 9th, 2026
Created on January 21st, 2011
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 423
Total Stargazers: 6,759 (+0)
Total Subscribers: 129 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.5 days
Mean response time: 325.8 days
90th percentile: 2120.0 days
Tracked items: 19

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

  • feature (8)
  • bug (5)
  • docs (2)
  • deppack (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Brunch is a build tool for web applications that compiles and bundles front-end code with a simple declarative configuration.

The tool addresses the need for fast, streamlined development workflows by providing seamless incremental compilation during active development and optimized production builds. It works through a watch mode that detects file changes and recompiles only what is necessary, enabling rapid iteration. For deployment, it offers a production build mode that applies minification and other optimizations by default. Projects are initialized from skeletons, which are boilerplate templates that can include framework-specific configurations, allowing developers to start with either a minimal setup or a pre-configured environment.

Brunch suits developers building web applications who prefer configuration over convention and want a straightforward build pipeline without extensive setup. The tool provides over fifty available skeleton templates covering different frameworks and libraries, so teams can choose a starting point matching their technology preferences. It is particularly useful for projects where fast incremental builds during development are a priority.

The project is deprecated and no longer maintained by its original author. Ownership of the package has been transferred to a new owner for an unrelated purpose, and the original maintainer has explicitly stated they have no affiliation with the new owner or their software. Users depending on this package are advised to pin to a specific final version from the original author and migrate to alternative tools where possible, as future versions will be published by a different author and should not be assumed safe to upgrade to without careful review.