Browser rejection hook

[benjamingr]

Hey, it would be great for us if you exposed the process unhandledRejection hook event somehow to browsers, this is useful for logging errors and handling problems.

Alternatively, if you make the isNode check overridable.

[zloirock]

Awaiting proposals how do it w/o breaking current default behavior and adding process module to browser bundles for all users. Or you mean this?

[benjamingr]

The problem is that it's a lot of code to run these browser events in old browsers. I think even just adding a window.onpossiblyunhandledrejection and not guaranteeing it will stay around is immensely useful.

[zloirock]

You mean simple

if(isNode){
  process.emit('unhandledRejection', reason, promise);
} else if(global.onunhandledrejection){
  global.onunhandledrejection({promise: promise, reason: reason});
} else if(global.console && console.error){
  console.error('Unhandled promise rejection', reason);
}

?

[benjamingr]

That would work and definitely aid a ton of people in debugging.

The main use case is that we have to include a bigger library (like bluebird) if we want any form of reporting of client side errors - which are useful in order to track errors users get so we can fix them.

[zloirock]

Ok, I will add it.

Warning: The problem here - we can't add it to native Promise implementations, but by idea core-js should use enough correct native implementation if it's available. Currently, most native implementations are buggy and core-js uses polyfill, but the situation will be changed. If someone wanna use this hook everywhere - he should delete window.Promise before inclusion core-js.