Contents
- Why choose Gulp?
 - Goals of a good Angular build
 - A working build and sample App
 - Why use a CSS pre-processor, and why Sass
 - The build-css task
 - Why use a module system
 - Why CommonJs is appealing
 - Angular now officially supports browserify
 - The build-js Gulp task
 - Angular-friendly Javascript minification
 - Pre-populating the Angular template cache
 - Reducing the number of HTTP requests using sprites
 - Why use cache busting?
 - Implementing cache busting with gulp-cachebust
 - Running tests with Karma
 - Code quality with JsHint
 - A development web server
 - Conclusions
 
Starting an AngularJs project also means choosing a whole toolchain that goes along with Angular. In this blog post we will propose a set of tools that a new Angular project will likely need, and present a simple Gulp build that provides those features. Let’s go over the following topics: