As secure $ENVs are disabled for pull requests and those $ENVs are required for running browser tests on saucelabs.

http://docs.travis-ci.com/user/pull-requests/#Security-Restrictions-when-testing-Pull-Requests

+ updated readme with the fact that browser tests are only runned automatically when *merged into master*, not in the PR stage

With 25 different browser versions it could easily take 15-25 minutes for a run too finish.
Only test latest chrome & firefox atm, increase support later as needed.

Removing hacks to get v0.6 tests running; specific npm client version + upgrading mocha.
Also v0.12 of node has been released, therefore there's no reason to still keep testing on v0.11.

Browser tests

Covers the project with browser tests, not only V8 via node/iojs. Tests are runned with [zuul](https://github.com/defunctzombie/zuul) which
provides simple local browser testing, aswell as cloud testing on multiple browsers with [saucelabs](http://saucelabs.com).

Due to eslint changes, pre-commit hook was failing to locate version in
mustache.js due to code using single quotes now, therefore "X.X.X" was
not longer matching, and had to be changed to 'X.X.X'.

BOM as whitespace test case

eslinting

added migration guide for v2

fixing null and undefined lookup

pre-commit hook refactoring, closes #432

Added `-v` option to CLI, bugfix for rendering `Number` when it was the
context, and specified files in package.json for cleaner `npm install`.

Specifying files in package.json

Good npm citizens should specify which files a npm module consists of
so module users dont have to download all the unnecessary things.

Bugfix for number rendered as [object Object]

+ minor fix for better error message when running specific render test

Fixes #415

CLI: -v option for displaying current version

Fixes #431

Created command line tool

Improve documentation to explain that Inverted Sections uses falsy

CLI used to render a mustache template with a data view, writes the template into stdout when successfull. Otherwise meaningfull errors into stderr.

Fixes #424

run jshint before tests, support of node back to v0.6

- Documented required version of npm while developing
- Use the latest npm client for node >= v0.8 on travis

Special quirks to get node v0.6 supported:
	- npm client v1.3.26 on travis
	- jshint 2.4.4 as >= 2.5.x breaks

Cleanup tests section in readme

Refactor Writer.renderTokens() for better readability.

Split the old Writer.renderTokens() into several small functions with a single responsible.

added pre-commit hook and hook installer, resolves #401

an image is wroth a thousand words

Conflicts:
	package.json