We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The naming of the events are slightly different, but should have same behavior.
https://googlechrome.github.io/samples/promise-rejection-events/index.html
I know pinkie is meant for Node.js, but people will still Browserify Node.js stuff that use it.
pinkie
The text was updated successfully, but these errors were encountered:
@sindresorhus Maybe you can give Yaku a try.
Sorry, something went wrong.
How should we handle the console output?
Chrome currently outputs a nice message that shows the rejected promise:
And then updates when it is later fulfilled:
(Note how the x changes to a check).
x
I have played with using window.dispatchEvent and it doesn't seem to output anything to the console. It only seems to work with native promises.
window.dispatchEvent
I am not sure we should be printing to the console at all, but doing so would better follow the native implementation.
No branches or pull requests
The naming of the events are slightly different, but should have same behavior.
https://googlechrome.github.io/samples/promise-rejection-events/index.html
I know
pinkie
is meant for Node.js, but people will still Browserify Node.js stuff that use it.The text was updated successfully, but these errors were encountered: