stream

node-fetch currently completely ignoring Content-Length header while consuming response.
Fetch specification about handling Content-Length on server response says almost nothing:
https://fetch.spec.whatwg.org/#concept-http-network-fetch (see whatwg/fetch#67)

On other hand, we have a fetch-node specific extension to limit the size of the response.

My prop

Platform: macOS

It should cover when you'd use and how to use:

• parEvalMap/Unordered
• parJoin
• concurrently
• merge*

There's the page on Queue/Topic/etc but there's not a great single page on the operations directly on Stream. The Guide section on concurrency is very short and doesn't cover some of the most common operations (parEvalMap especially)