Stream.prototype.forEach will block in first promise in queue before read more chunk
Open
Beginner friendly
Nobody has claimed this yet.
doc
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Affected URL(s)
No response
Description of the problem
The forEach supports concurrency run fn on chunk, but actually it implements by map which causes that before first promise in queue ends, it doesn't read more chunk and run into queue.
I think doc should clear this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Stream.prototype.forEach documentation and reviewing its concurrency wording against the described queue behavior. Done when the documentation clearly explains whether additional chunks are read while earlier promises are pending.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100