Ask questionsSummit Topic: Node.js Streams promise support

<!-- Thank you! You are submitting a topic for the next Collaborator's Summit, Montreal 2019!

Please include as much detail as you are able to at this moment. Don't worry, it doesn't have to be complete.

Please feel free to link to any other issue, PR, or resource that could be relevant. -->

Topic of the session

We have added async iterators to stream a quite successfully! It's time to think of what's missing.

Type of the session

  • [x] Collaborate
  • [ ] Workshop
  • [ ] Talk

Follow-up / Set-up sessions (if any)

List the sessions that are related.


  • [] Beginner
  • [] Intermediate
  • [] Advanced

Pre-requisite knowledge

List pre-requisite knowledge that it would be required for participants to have.

Describe the session

Session facilitator(s) and Github handle(s)

<!-- Here's a handy guide for the person or persons who will facilitate this session. -->

Additional context (optional)


Answer questions apapirovski

That's much neater haha

which is arguably confusing

Yeah, I was just taking off from where Jeremiah left it. I can see why some people would want to have the option to not get unhandled rejections in certain scenarios when using the promisified API.

(Also need to handle the error event which I forgot to do, but yeah...)


Related questions

Summit Topic: Promises in Node.js Core hot 1
Summit Topic: Streams (Node.js) hot 1
Community Corner: How to contribute to open source using Git and GitHub hot 1
Summit Topic: Streams (Node.js) hot 1
Github User Rank List