Question 1

How do I use duplexify to handle HTTP requests and responses as one stream?

Accepted Answer

Create a duplexify instance, attach the HTTP request as the writable part, and on response, use setReadable() to attach the response stream. This allows you to pipe the entire HTTP interaction as a single duplex stream, simplifying client-side code.

Question 2

duplexify vs duplexer2: which should I use?

Accepted Answer

Use duplexify if you need support for both streams1 and streams2 or async stream attachment; duplexer2 is limited to streams2 and synchronous initialization. duplexify offers more flexibility for legacy compatibility and delayed stream setup.

Question 3

Does duplexify support object mode streams?

Accepted Answer

Yes, use duplexify.obj(writable, readable) to create an object-mode duplex stream directly. This is useful for pipelines handling JSON, buffers, or custom objects without manual mode setting.

Question 4

What happens if I call setReadable multiple times in duplexify?

Accepted Answer

Calling setReadable() or setWritable() multiple times unregisters the previous stream and attaches the new one. To disable a part, set it to null, giving you control over dynamic stream lifecycle changes.

Question 5

Can I use duplexify with async/await or promises?

Accepted Answer

While duplexify itself is event-based, you can wrap it in promises using stream events or utilities like pump. However, it doesn't provide native Promise APIs, so additional code is needed for modern async patterns.

Question 6

How does duplexify handle stream destruction on errors?

Accepted Answer

If either the readable or writable stream emits an error, duplexify automatically calls destroy() on both streams and bubbles up the error event. You can also trigger this manually with dup.destroy(error) for custom error handling.

duplexify

What is duplexify?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions