Awesome, thank you!

I wonder, if we should move Error.call(this) to the top to set name, message etc. afterwards. In V8 that is not necessary. But how about the other browsers? What would you prefer?

I tested this order in Firefox and IE (latest). So I would leave it as it is.

I just looked into Error.call(this) and as far as i can tell now it doesn't work as intended. See the section "Obstacle 2: a constructor that can’t be called as a function" in http://www.2ality.com/2011/12/subtyping-builtins.html
Any knowledge you can dump on me?

BTW, the test failed due to a timeout. Your PR was working fine.

One specific question: In Firefox and IE do the errors have a stack property? (According to the blog post they won't. But the blog post may be wrong.)

Firefox does have a non-standard stack property. See https://developer.mozilla.org/de/docs/Web/JavaScript/Reference/Global_Objects/Error/stack

And IE also has a stack property. See
https://msdn.microsoft.com/library/ie/hh699850(v=vs.94).aspx/

So it would be possible to write the stack trace to the console.

Regarding the Error.call(this) the blog post seems right. Probably it would be the best to check for the stack property if Error.captureStackTrace is not available.

Alright, I keep the if (Error.captureStackTrace) but remove the Error.call(this).

Thanks for your feedback!

I just published v0.4.1 on NPM.