Return an exit code on error

This allows an errback to be optionally passed into compile_project. The
roots binary then takes advantage of this functionality to pass in an exit
handler. I also modified the general compile test to fail if an error is
thrown on a successful compile.
Merge pull request #331 from aawilson/feature-exit_code_on_fail

Return an exit code on error
correct path in generator log
Merge pull request #342 from wenzowski/feature/pathfix

correct path in generator log
adding git link
Merge pull request #359 from ajkochanowicz/master

adding git link
update the man page

add --no-open from #257
add list of bower commands to pkg
fix some formatting things in the man (some lists were formatted as
code blocks and some args were listed incorrectly)
update the readme on how to update the man page
get rid of whitespace at the end of lines in favor of <br>
update the help summary (w/ coffee)
Merge pull request #329 from jenius/update-manpage

Update manpage
2.1.1 :shipit:
[fix] catch template precompile errors

Fixes a race condition with the precompiler where we were not returning
a promise, and thus it was continuing down the compile chain while files
were still being compiled

This also fixes the issue of the roots watch command hard exiting when
an error occured while compiling the jade

fixes #361
Merge pull request #362 from jenius/sjs/fix-precompiler

[fix] catch template precompile errors
2.1.2 :shipit:
add file & docs for editorconfig.org
move license out of readme into standard file

also list it in package.json
compile coffee to js before publishing

closes #336
prepublish gets run during `npm install`, which can screw stuff up
so do it in a Makefile
see issue: https://github.com/isaacs/npm/issues/3059
test with 0.10 too
remove jquery from browser_assets

missed this in d6c112b4dd69f0c4acbf428b67bcf6f355ad410a
Merge pull request #360 from jenius/don't-break-the-logs

don't break the logs
Properly display errors that are not 'Errors'

This is was initially brought up to fix a problem with YAML errors
being reported as 'undefined'. It should now show the result of the
object's toString, or the object stringified if the toString looks
unhelpful.
added terminal_printer 'normalize_error' method