4 ms·
Something's missing in the "Modern Event Handling with AsyncIterators" section. The demonstration code emits events, but nothing receives them. Hopefully some
by jmull 1y ago
Something's missing in the "Modern Event Handling with AsyncIterators" section.
The demonstration code emits events, but nothing receives them. Hopefully some copy-paste error, and not more AI generated crap filling up the internet.
- yesbabyyes 1y agoIt's definitely ai slop. See also the nonsensical attempt to conditionally load SQLite twice, in the dynamic imports example. The list of features is nice, I suppose, for those who aren't keeping up with new releases, but IMO, if you're working with node and js professionally, you should know about most, if not all of these features.
- steve_adams_86 1y agoHasn't AsyncIterator been available in Node for several years? I used it extensively—I want to say—around 3 years ago. It's definitely awesome but doesn't seem newsworthy. The experimental stuff seems more along the lines of newsworthy.
- jay-barronville 1y ago> Hasn't AsyncIterator been available in Node for several years? I used it extensively—I want to say—around 3 years ago. Yes. It's been around and relatively stable in V8/Node.js for years now.
- jappgar 1y ago(Async) Iterators are definitionally pull-based and not suitable for event (push) handling. They've also been around for years as another poster mentioned.