Petka Antonov

@domenic In the [original email](http://lists.w3.org/Archives/Public/public-whatwg-archive/2014Sep/0024.html) you suggested `unhandledrejection` and `rejectionhandled` and the camelCased versions as per node convention are `unhandledRejection` and `rejectionHandled`. I went with `unhandledRejection` because it is in...

Pr welcome? :D

I had an idea of proprietary v8 core dumps that could be opened in Chrome debugger and debugged just as well as you can debug chrome web apps live in...

Yes and even if you are ok without having long stack traces, such mechanism still needs to be used so that proper core dump can be made after the actual...

Actually short stack traces might be very feasible as you don't actually need to collect them until an error happens. And long stack traces could still be separately enabled for...

Chrome debugger is more accessible and familiar to web developers, it's same software that works cross platform and you can get long stack traces rather than just the last event....

Both (recover object and recover method) are non-standard promise API extensions that will be obsoleted when the standard catch statement is extended to support custom predicates

@DonutEspresso You are using unexpected/expected errors to mean operational/programmer errors. The distinction, and what @spion means, is supposed to be that whether an error is unexpected/expected is decided by the...

A completely separate module can be blacklisted so that concerns such as promises ruining existing post-mortem workflows with callbacks can be addressed by simply blacklisting the separate module as people...

It's a bug in jsdom, see https://github.com/jsdom/jsdom/issues/3818#issuecomment-2677541896