Fixed namespace leak
2.1.5
2.1.6
Update mocha to 1.17.1.
Don't require a build step in node.js.

Instead, add a main module that creates a new vm context, then evaluates the sources files in it one by one and exports weknowhow.expect from it.
test/common: Use /index instead of the built /lib/unexpected.

This makes regular mocha work, although it currently relies on "common" being asciibetically < "unexpected.spec.js"
Format errors as '[Error: <message>]' rather than '{}'.

Fixes #22.
Build unexpected for production
2.1.7
Make overriding inspect on custom types work in the browser
Build unexpected for production
2.1.8
Removed unexpected-es4-compatible.js from index as node is es5 compatible
Merge pull request #30 from sunesimonsen/eliminateBuildStepForNodeJsAndMocha

Eliminate build step for node js and mocha
Fixed wrong character in main name
Removed es5 killer script for development testing as it makes ruins the browser runner
Make the standard assertion error available without throwing
Fixing jshint errors
Lint test files
Handle nested expects inside of custom assertion in a more controlled
manner

Changes the default handling of nested expects inside assertions to use
the standard error message for the assertion instead of the error
message of the nested expect.

Two new boolean flags has been added to the assertion in order to
control how error messages of nested expects are handled.

* bubbleExpectErrors: use the error message of the nested expect
* nestExpectErrors: show the standard error for the assertion followed
  by the error message of the nested expect.

Example of the default behaviour:

```js
expect.addAssertion('to be a number with value', function (value) {
    expect(this.obj, 'to be a number');
    expect(this.obj, 'to be', value);
});
expect('42', 'to be a number with value', 42);

// throw: expected '42' to be a number with value 42
```

Example of bubbleExpectErrors:

```js
expect.addAssertion('to be a number with value', function (value) {
    this.bubbleExpectErrors = true;
    expect(this.obj, 'to be a number');
    expect(this.obj, 'to be', value);
});
expect('42', 'to be a number with value', 42);

// throw: expected '42' to be a number
```

Example of nestExpectErrors:

```js
expect.addAssertion('to be a number with value', function (value) {
    this.nestExpectErrors = true;
    expect(this.obj, 'to be a number');
    expect(this.obj, 'to be', value);
});
expect('42', 'to be a number with value', 42);

// throw: expected '42' to be a number with value 42
              expected '42' to be a number
```

This works recursively of cause.

------------------------------------------------------------------

After doing this change I need to fix the output of some of the
assertions and change the test to expect the improved error messages.