`version` is currently a moot prop since git tags are used instead. More
info at https://github.com/bower/bower.json-spec/commit/a325da3.

Remove moot `version` property from bower.json

Per bower/bower.json-spec@a325da3

Fix view prototype value lookup issues

Fixes #445

Bugfix for view context cache

Fixes #442

Only display result of master branch on travis badge

Closes #450

Minor changes to make it compatible with both WSH and ASP (eslint com…

Added the keywords "imports", "nested" and "subtemplates" to the docs

Improve CLI parsing error

Made it eslint compatible.

Add license attribute

https://docs.npmjs.com/files/package.json#license
http://npm1k.org/

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.