You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
I've noticed that with default Meteor's then/promise polyfill there is no way to catch unhandled rejections. then/promise#70
To solve this I'm looking for some way to replace then/promise with petkaantonov/bluebird, since bluebird can do process.on("unhandledRejection", function() {...})
I've tried to meteor add mvrx:bluebird, but looks like Meteor's core promise polyfill hides bluebird since "unhandledRejection" does not catch, and this fails: if (!Promise.noConflict) { throw Error('NO BLUEBIRD'); }
Any ideas?
The text was updated successfully, but these errors were encountered:
I've been thinking about reducing the scope of this package so that users have to provide their own Promise implementation, which should make it easier to use in an existing environment where you already have a preferred polyfill. Would that be better for you, even though you found a workaround in this case?
I've noticed that with default Meteor's
then/promise
polyfill there is no way to catch unhandled rejections.then/promise#70
To solve this I'm looking for some way to replace
then/promise
withpetkaantonov/bluebird
, since bluebird can doprocess.on("unhandledRejection", function() {...})
I've tried to
meteor add mvrx:bluebird
, but looks like Meteor's core promise polyfill hides bluebird since"unhandledRejection"
does not catch, and this fails:if (!Promise.noConflict) { throw Error('NO BLUEBIRD'); }
Any ideas?
The text was updated successfully, but these errors were encountered: