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
Actually, nvm, you do detect it (it's just there is no uncaught error warning). My issue turns out is that I'm calling then before I return the chained promise:
var b = Promise.resolve().then(function() {return b.then(function() {return 1;})});
This obviously, never finishes, yet it's not detected.
Indeed, your original example is covered by the Promises/A+ test suite, so we definitely detect that.
The later example is (as discussed on twitter) vastly more complex to actually detect. If you think it's worth while, we could look into adding more advanced cycle detection, as long as we do it in a way that can be stripped out for production, i.e.
all work is done in if (process.env.NODE_ENV !== 'production') so that there is no performance impact in production.
It can only log/warn for errors, it must not reject any promises that would otherwise be fulfilled.
Both native promises in Chrome and Bluebird has that.
The text was updated successfully, but these errors were encountered: