> I still think the best solution to this is for the developer tools to
> curate a list of unhandled rejections. Just like `window.onerror` and the
> developer console work together to display unhandled exceptions, unhandled
> rejections could be treated very similarly. They would appear in the
> console while unhandled, then disappear when/if handled. (And there could
> be programmatic hooks too, just like window.onerror, e.g.
> `window.onunhandledrejection`/`window.onrejectionhandled`.)
>
That could certainly work for browsers, but what about node and its console?
Also, can someone point me to a real-world example of delayed rejection
handling?
{ Kevin }
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
