Not so long ago,
a simple project could get away with hacking some code
into a single
include it in a
and be done with it.
With the rise of ES6
and the modularization of libraries
building out the final file can be fairly complicated.
So, let me jump to the conclusion:
The other tools that I examined have their place, but here are some reasons why I like Brunch.
1. Very little setup
Brunch follows a convention over configuration style. This means that there isn’t much to put into the configuration file. Play by the rules (of which there are few) and it will typically do The Right Thing™.
2. Use ES6 with almost no thought
you have to deal with a transpiler like
ES6 is only a single plugin away (
from automatically working with Brunch.
3. Three commands in total. Yes, three!
$ brunch new $ brunch build $ brunch watch
brunch new will help you bootstrap a new project.
Because of the use of conventions,
this is the recommended way to get started.
The command will set up all the structure you need
to get creating.
With the help of some project templates called skeletons,
you can even get initial plugin configuration out of the way.
Try it with:
$ brunch new -s es6
brunch build and
The two are related with one big distinction:
the latter will watch the files in your project
and incrementally update the output
whenever something changes.
Watching your project for changes is a powerful paradigm
used by many of the tool chains out there,
and it’s nice that Brunch also has that feature.
I think I can read your mind:
If you want to chat about this with me, I'm @mblayman on Twitter.
What I learned about the Python standard library and how you can apply those learnings to your own study.
Matt is the lead software engineer at Storybird.
Always eager to talk about Python and other technology topics, Matt organizes Python Frederick in Frederick, Maryland (NW of Washington D.C.) and seeks to grow software skills for people in his community.