-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
Move stream development out from core #43520
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@nodejs/streams @mcollina |
In a practical sense this means:
|
@targos I believe we might need your help to do this. |
Sure, on what front? |
Assuming there is consensus. Setting up the workflow with merging readable-streams into core similar to what we do with undici. |
What benefit would moving it out of core give us? |
Easier to develop and easier to keep the ecosystem up to date. I believe @mcollina can better articulate the benefits. |
I'm +0 on this |
I'd be +1 on this with the caveat that we need to continue to carefully deal with breaking changes in the streams API. So long as that continues to be a priority, I've no problems with moving this piece out. |
Now that https://github.com/nodejs/readable-stream is up to date with the latest node version I would like to bring up the discussion of moving development of stream out of core in a similar way we currently do with undici.
The text was updated successfully, but these errors were encountered: