Possibly unhandled error should be thrown
See original GitHub issueNode v0.10, non-harmony. Such as:
var Promise = require('bluebird');
new Promise(function () { throw('err') });
// Unhandled error will be thrown.
var Promise = require('es6-promise').Promise;
new Promise(function () { throw('err') });
// Nothing will happen.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:2
- Comments:44 (12 by maintainers)
Top Results From Across the Web
Angular 1.6.0: "Possibly unhandled rejection" error [duplicate]
This is a big problem for me currently as I'm migrating a code base and replacing an old injected dependency.
Read more >Angular 1.6's Possibly unhandled rejection errors - codelord.net
Essentially, this error is printed to the console whenever a promise in your app is rejected (resolved with a failure), and there's no...
Read more >Error handling with promises
Usually such errors are unrecoverable, so our best way out is to inform the user about the problem and probably report the incident...
Read more >Tracking Unhandled Promise Rejections - TrackJS
Before we can look at error handling in promises, it is useful to see a simple ... throws up its hands and produces...
Read more >Handling those unhandled promise rejections with JS async ...
You put an await call inside a try/catch block or you use .catch(); The await ed function fails (i.e. rejects a promise); You...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ya, still trying to find time 😉 It will land, I was a big proponent of the feature in the first place.
Chrome currently logs unhandled errors. Firefox does it on GC.
Happy to do the same as Chrome here. It should be a log rather than a throw, we’d be spec-breaking if it appeared in
window.onerror
.