Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams
by drapper on Wednesday January 28, 2015 @06:13AM
(#8959171)
...and you can also have something like that using Bluebird.coroutine() (https://github.com/petkaantonov/bluebird/blob/master/API.md#...) or co (https://github.com/tj/co, see also https://github.com/koajs/koa)
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams
by phpnode on Wednesday January 28, 2015 @08:09AM
(#8959550)
6to5 actually supports compiling async/await to bluebird coroutines
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams
by davedx on Wednesday January 28, 2015 @08:02AM
(#8959520)
Whaaa... they're putting experimental ES7 features in a transpiler called 6to5? Or am I missing something?
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams
by phpnode on Wednesday January 28, 2015 @08:11AM
(#8959560)
Its getting a new name: https://github.com/6to5/6to5/issues/596
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams
by aeosynth on Wednesday January 28, 2015 @08:10AM
(#8959555)
The project scope has expanded: https://github.com/6to5/6to5/issues/568
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams
by soaringmonchi on Wednesday January 28, 2015 @06:29AM
(#8959210)
Definitely my preferred approach. Note that you need to run 6to5 with the -e flag to try this.
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams
by thejameskyle on Wednesday January 28, 2015 @11:36AM
(#8960823)
I think you mean the --experimental flag. -e is for evaluate.
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams
by jonpaul on Wednesday January 28, 2015 @07:12AM
(#8959354)
Where does it say that it supports async/await?
[0]: http://6to5.org/