This is an attempt at a comprehensive guide to Brunch, an excellent builder for browser apps that gives Grunt, Gulp, Broccoli et al. a run for their money. I adapted this from my (French language) article from early March 2015.
Is your English reading not so good? Check out our translations.
- Brunch vs. others
- Task runners vs. builders
- File-based processing vs. pipelines
- Configuration and boilerplate vs. conventions
- Full builds vs. incremental builds
- The paramount importance of speed
- Then why do I only ever hear about the others?
- Built-in processing
- Configuration files
- Folders
- CommonJS module wrapping
- Sourcemaps
- Watcher
- Built-in web server
- Plugin loading
- How about a shortcut?
- Just a couple files
- Installing a starting set of Brunch modules
- Our first build
- Globals; because, reasons.
- Getting modular again
- Split targets
- Using third-party module registries
- A shot at templating
- Using Brunch on a legacy codebase
- Production builds
- Watcher
- Web server: built-in or custom
- Enabling a plugin
- Fine-tuning through optional configuration
- Brunch and CSS
- Brunch and JavaScript
- Brunch and templates
- Brunch and development workflows
- Brunch and web performance
This guide is also available in the following languages:
To contribute translations, check out our guidelines.
This guide was written against Brunch 1.7.20. Most of it likely works in earlier 1.7.x versions, but may need updates when the upcoming 1.8 or 2.0 gets out (especially WRT npm / node_modules integration).
This work is © 2015 Christophe Porteneuve, licensed under the MIT license.
I welcome all useful contributions: typos, bug fixes, rephrasings, better explanations or examples, extra information and demos, translations, etc.
Be sure to check our contribution guidelines!
The Brunch team deserves enormous applause and thanks for their amazing work on this tool. I write this as Brunch turns 4 already, and it's made my life easier (and that of hundreds of my JS trainees) for all that time! You guys rule!