Previously mocha, uglifyjs and jshint used when publishing a new version were ensured / installed by `Rakefile` via the pre-commit git hook. Those modules were automatically installed globally if not present in `$PATH`.

Installing modules globally has one particular downside that we should avoid: we can't ensure developers publishing new mustache.js versions have the same version of these 3rd party modules installed.

If instead we make these modules local dev dependencies, we can ensure which versions are installed, and we make 3rd party dependencies explicit by listing them in `package.json`, rather than in `Rakefile`.

First shot at getting greenkeeper to ignoring eslint updates landed with commit 85fa743258.

Sadly that commit had a minor `greenkeper` misspelling in package.json, which obviously didn't have much effect for greenkeeper.
This commit fixes that blooper in hopes that greenkeeper will stop opening PRs about new eslint versions, as we don't want to
update at the moment cause eslint 3.x requires Node.js v4.x.

https://greenkeeper.io/

https://greenkeeper.io/

As we don't plan to update to Node.js v4 any time soon,
we can't update eslint cause it requires Node.js => v4.

http://greenkeeper.io/

http://greenkeeper.io/

greenkeeper.io will let us know if the minor/patch bumps break our code, so go wild.

http://greenkeeper.io/

http://greenkeeper.io/

http://greenkeeper.io/

http://greenkeeper.io/

http://greenkeeper.io/

http://greenkeeper.io/

Also minor .eslintrc change to be able to use `process.exit()`,
instead of having to `throw new Error()` to exit the process.

http://greenkeeper.io/

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

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.

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).

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

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

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

- 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

This change allows the AMD define signature to match what common AMD optimizers use to find define calls that need naming.
Also updates the volo package.json entry so that the correct version of mustache can be fetched properly.

The goal is to reduce the number of files downloaded by ignoring the test directory