yosh

@jaffathecake @cramforce

@brianleroux @jaffathecake @cramforce the error swallowing thing is *addressed* not really *solved*.

@mikeal @brianleroux @jaffathecake @cramforce i can't be the only one who has had my callbacks swallow errors on numerous occasions

@sebmck @brianleroux @jaffathecake @cramforce you can totally ignore that first parameter :) you're just likely to get a different exception

@mikeal @sebmck @cramforce just as you can ignore the .catch and console message

@mikeal @sebmck @cramforce does node log on unhandled rejection? Would be great if it did.

@jaffathecake @sebmck @cramforce even better, there's a global handler for it on `process` :)

@mikeal @sebmck @cramforce excellent! (Chrome does both, fwiw)