-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Streams mini summit #18640
Comments
Also @nodejs/tsc. |
sorry I haven't been very active lately so I'd probably not be able to make a summit in person. |
Where might this take place? I'm helping to lead the 'future streams' initiative (current work at https://github.com/Fishrock123/bob) - I'm not sure how relevant that would be yet though? |
@Fishrock123 I think we have a full day of work for this (or multiple calls). Topics:
We can also start takling some of these remotely, if an in-person meeting is not be feasible. |
Accidentally stumbled upon this one, I think it can be closed already? |
Yes! |
I've been talking to @mcollina about having another streams mini summit.
We've been doing a lot of streams maintenance lately, (especially @mcollina), and would love to meetup with the WG and talk about how to iterate node core streams.
Some initial thoughts in no particular order
a stream should never emit data after .destroy()
) - Would make bug fixing / maintenance much easier if we had some clear behavior definedThoughts? @nodejs/streams
The text was updated successfully, but these errors were encountered: