[OMD-123]

Describe the bug

A regression was introduced in Node.js where Duplex.from(async () => {}) triggers an unhandled AbortError. This occurs because the async function resolves without consuming its input, and the implementation calls destroyer(d), which synthesizes an AbortError for any stream that is not yet finished.

The Fix

I have replaced the call to destroyer(d) with d.destroy() in lib/internal/streams/duplexify.js.

Unlike destroyer(), d.destroy() cleans up resources without synthesizing an artificial error. Since the async function resolved successfully, there is no actual error to report, and a duplex outside of a pipeline has no listeners for one.

Testing done

I have implemented a hardened regression test suite in test/parallel/test-duplex-from-hardened.js covering:

• Basic Regression: Verified that Duplex.from(async () => {}) no longer throws ABORT_ERR.
• Partial Consumption: Verified that partial consumption of input also resolves cleanly.
• Error Fidelity: Confirmed that if the async function throws its own error, that error is propagated correctly and not masked by an AbortError.
• Pipeline Integration: Verified that the fix does not break stream.pipeline()'s destruction propagation.

All tests pass on Node.js v22.23.3.

Fixes #66349

[nodejs-github-bot]

Review requested:

• @nodejs/streams

[github-actions]

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

• the guide for first-time contributors
• the contribution and automation policies
• the pull request guide
• the AI use policy
• the Code of Conduct

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

[OMD-123]

Hello @nodejs/streams, I have implemented the fix and added a hardened regression test suite covering several edge cases. The PR is currently in needs-ci state; I would appreciate it if a triager could trigger the CI run. Thank you!

[OMD-123]

Hello @nodejs/streams, I have implemented the fix and added a hardened regression test suite covering several edge cases. The PR is currently in needs-ci state; I would appreciate it if a triager could trigger the CI run. Thank you!

[inoway46]

Closing as a duplicate of #66243, which makes the same fix. Any additional regression coverage can be discussed there.