es6-promise

Or you could add a fetch polyfill with zero dependencies: https://github.com/github/fetch/blob/master/package.json And a Promises library with zero dependencies: https://github.com/stefanpenner/es6-promise/blob/master/pack... This is not as difficult as you're making it out to be.

I disagree. A developer choosing to not handle the 'error' param in an error-first callback at all is incompetence from a node dev, akin to writing 'try-except-pass' in Python, whereas silent swallowing of runtime exceptions is a bug of the runtime and inexcusable. Btw, I prefer Promises and the error-bubbling approach in principle for the reasons you're getting at, but the current implementations (especially in p0lyfills like es6-promise) are simply broken, due to the standards themselves being lacking. See this comment for fact the fix has been in draft for a while now: https://github.com/stefanpenner/es6-promise/issues/70#issuec...

Unfortunately Promises need to be fixed before fetch will be sane and here's how the promises spec currently looks: - unhandled errors silently swallowed [1] (this is the case for the most popular polyfill [1] too - the one recommended by fetch polyfills, BEWARE [3]) - no 'finally' method, despite pretty much everything in a UI needing some common 'cleanup' after e.g. a fetch() - not cancellable Right now you're better off with `$.ajax` (maybe make a custom build of jQuery) or a promise-like library like reqwest [2], rather than fighting with fetch. [1] https://github.com/stefanpenner/es6-promise/issues/70#issuec... [2] https://github.com/ded/reqwest [3] http://requirebin.com/?gist=8f13d5147c1c252ab1691115bfa8b7c5