anyone seen issues with letting errors propagate out of pr/loop only on cljs ? i've got some promesa-based code i'm porting from clj to cljs, and i've come across several cases where the code seems to work semantically correctly on cljs, but causes a crash (at least on node) because of an uncaught rejected promise... catching all errors inside the loop seems to fix the problem