You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 3, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 3, 2026. It is now read-only.
We should remove duplexify. In all cases where it is used today, native Node.js Stream options, namely Transform, make more sense.
Today Duplexify streams are passed around to too many functions and have lots of random ‘side effects’ to keep track of; leading issues that are difficult to debug. A refactor using native Node.js streams and pipelines will make things much more straightforward and would shrink the overall codebase. For example, we can trust the 'close' event more in native streams than in the duplexify implementation; namely in the cases of requests (duplexify streams 'close' before a 'response' is received).
This is a breaking change as duplexify.Duplexify is exposed as a return type in some public APIs.
As an additional note, in the future we can move to the Web Streams API for web compatibility - moving to Node.js Streams first will make this step much easier as the Readable, Writable, and Transform implementations are similar.
Reacted by Nick Porter, Maxime Bernard, kirrg001, Cheskel Twersky, Takanobu Hoshino, Paul Nispel and Martin Piták
Activity