3 ms·
Does koa (or co) solve the problem with generators where * stack traces of errors are useless? [1] * missing catch filters/pattern matching i.e. catch (e) {}
by spion 13y ago
Does koa (or co) solve the problem with generators where
* stack traces of errors are useless? [1]
* missing catch filters/pattern matching i.e. catch (e) {} also captures type, reference and range errors i.e. "pokemon exception handling"?
[1]: http://spion.github.io/posts/analysis-generators-and-other-async-patterns-node.html#stack-trace-accuracy http://spion.github.io/posts/analysis-generators-and-other-a...
- jongleberry 13y agoyes, stack traces work now, as long as they aren't being thrown in a different event loop: https://github.com/koajs/koa/issues/117 https://github.com/koajs/koa/issues/117
- spion 13y agoOops - I didn't mean thrown errors, I meant errors passed to the callbacks. It doesn't seem like they are useful yet: https://gist.github.com/spion/356bfc9cc1089edd2e3b https://gist.github.com/spion/356bfc9cc1089edd2e3b