beautify errors

[tunnckoCore]

• better https://github.com/azer/prettify-error
• better formatting
• support custom templates
• support custom object context
• his failing-line and failing-code are awesome, use it
• NO STACK TRACES BY DEFAULT, YEA I HATE THEM!!!

this is far more useful and clean

  ✖ should return true if given `name` not exist in npm registry

    AssertionError at /home/charlike/dev/test.js: line 34, column 22-25

                               vvv
    33.   isMissing('wombat-foo-bar-baz-qux-zero-four', function _cb(err, res) {
    34.     assert.strictEqual(123, null);
    35.     assert.strictEqual(res, true);
                               ^^^

     actual: 123
   expected: null
   operator: ===
    message: 123 === null

  ✔ should return false if given `name` exist in npm registry
  ✔ should return true if given `name` not exist in npm registry

answering

• what is the error name? - AssertionError
• from where? - path to file
• from which line? - 34, also prev and next lines are shown
• what is actual value? - 123
• what is expected? - null
• what is the error message? - in case pretty simple '123 === null'
• god damn, your eyes are okey!

[tunnckoCore]

YEAH, mocha tuned down the fcking stack straces

[tunnckoCore]

hint https://github.com/jonschlinkert/plugin-error

[tunnckoCore]

var PackageError = require('package-error')('my-pkg-name') // in `debug` style

var realErr = new TypeError('expect `name` to be string')
throw new PackageError(realErr, {actual: typeof name, expected: 'string'})

[tunnckoCore]

have process on this.. kind-error, error-format, stacktrace-metadata, error-base, useful-error.