Fix 1875: Markdown reporter exceeds maximum call stack size

Fix #1864: xunit missing output with --reporter-options output

…the browser

"Expected a conditional expression and instead saw an assignment"

Support all harmony flags

Fix fragile xunit reporter spec

Unfortunately some frameworks throw error objects which do not have a `message`
property but do have an `inspect()` function. This means Mocha reports a test
failure, but prints the empty string instead of any useful information about
the error message. For an example, see versions of the Waterline ORM before
v0.10.19: balderdashy/waterline@0965d132

If the `message` key is not set on an error object, attempt to print the same
output as `console.log` in Node, by calling the object's `inspect()` function,
if it exists.

We could try to fallback to calling `util.inspect` on the `err` object and
logging that, but I'm not sure the format would be appropriate.

Fix #1669: catch uncaught errors outside test suite execution

Revert jade to support npm < v1.3.7

Stackfilter fix: Don't remove modules/components from stack trace in the browser

Fix #1798: Correctly attribute mutiple done err with hooks

Relevant: npm/npm#9668