Stream Whack a Mole

Explore a comprehensive conference talk on Node.js streams, their evolution, and common pitfalls. Dive into the complex world of P2P Node.js Core Streams, uncovering potential bugs in stream implementations. Trace the history of Node.js Streams through various iterations, from Streams 1 to Streams 3, and understand the challenges faced in maintaining backwards compatibility. Learn about critical issues such as memory leaks, magic behaviors, and error handling in streams. Gain insights into best practices for stream implementation and discover the future direction of streams in Node.js, including improved error handling and lifecycle support. Perfect for developers seeking to deepen their understanding of Node.js streams and avoid common mistakes in their implementations.

Intro
P2P Node.js Core Streams
A depressing story on why you probably all have bugs in your streams
A Brief History of Node.js Streams
Streams 1
Streams 2 - Node.js 0.10
Complex Batteries included Pull based
Streams 3 - Node.js ~0.11
Small iteration on
Makes the s.on('data') work together with the
Streams are still evolving
Everytime we fix a bug we break tons of things
Streams are probably the most complex objects returned from Node.js core
readable-stream is an official npm mirror of stream(node)
Memory leak. Always drain your streams node
Yes, on('data') has magic behaivor
does not mean end
Backwards compat
pipe() does not do error handling
Never use pipe()
The Future
Makes streams easier to implement de
Error handling pipe, proper life cycle support, backwards
Thank you!