ngbp | sophisticated build management system for web apps | Frontend Framework library

Install Node.js and then:. Finally, open file:///path/to/ng-boilerplate/build/index.html in your browser.
This section provides a little more detailed understanding of what goes into getting ngBoilerplate up and running. Though ngBoilerplate is really simple to use, it might help to have an understanding of the tools involved here, like Node.js and Grunt and Bower. If you're completely new to highly organized, modern JavaScript development, take a few short minutes to read this overview of the tools before continuing with this section.
The best way to learn about the build system is by familiarizing yourself with Grunt and then reading through the heavily documented build script, Gruntfile.js. But you don't need to do that to be very productive with ngBoilerplate. What follows in this section is a quick introduction to the tasks provided and should be plenty to get you started.
delta:gruntfile - When Gruntfile.js changes, this task runs the linter (jshint) on that one file and reloads the configuration.
delta:assets - When any file within src/assets/ changes, all asset files are copied to build/assets/.
delta:html - When src/index.html changes, it is compiled as a Grunt template, so script names, etc., are dynamically replaced with the correct values configured dynamically by Grunt.
delta:less - When any *.less file within src/ changes, the src/less/main.less file is linted and copied into build/assets/ng-boilerplate.css.
delta:jssrc - When any JavaScript file within src/ that does not end in .spec.js changes, all JavaScript sources are linted, all unit tests are run, and the all source files are re-copied to build/src.
delta:coffeesrc - When any *.coffee file in src/ that doesn't match *.spec.coffee changes, the Coffee scripts are compiled independently into build/src in a structure mirroring where they were in src/ so it's easy to locate problems. For example, the file src/common/titleService/titleService.coffee is compiled to build/src/common/titleService/titleService.js.
delta:tpls - When any *.tpl.html file within src/ changes, all templates are put into strings in a JavaScript file (technically two, one for src/common/ and another for src/app/) that will add the template to AngularJS's $templateCache so template files are part of the initial JavaScript payload and do not require any future XHR. The template cache files are build/template-app.js and build/template-common.js.
delta:jsunit - When any *.spec.js file in src/ changes, the test files are linted and the unit tests are executed.
delta:coffeeunit - When any *.spec.coffee file in src/ changes, the test files are linted, compiled their tests executed.
To make the build even faster, tasks are placed into two categories: build and compile. The build tasks (like those we've been discussing) are the minimal tasks required to run your app during development. Compile tasks, however, get your app ready for production. The compile tasks include concatenation, minification, compression, etc. These tasks take a little bit longer to run and are not at all necessary for development so are not called automatically during build or watch.