René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"stream: Duplex.from errors when async function body resolves without consuming its input","articleBody":"### Version\n\n26.10.0\n\n### Platform\n\n```text\nAll\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nThe bug, as of node 26.10.0:\n\n```\nnode -v\nv26.10.0\nnode -e \"require('node:stream').Duplex.from(async () => {})\"\nnode:events:505\n    throw er; // Unhandled 'error' event\n    ^\n\nAbortError: The operation was aborted\n    at destroyer (node:internal/streams/destroy:328:11)\n    at node:internal/streams/duplexify:120:13\nEmitted 'error' event on Duplexify instance at:\n    at emitErrorNT (node:internal/streams/destroy:170:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:129:3)\n    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {\n  code: 'ABORT_ERR'\n}\n\nNode.js v26.10.0\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nThe original behavior, as of node 26.9.0:\n\n```\nnode -v\nv26.9.0\nnode -e \"require('node:stream').Duplex.from(async () => {})\"\n// no output; this is expected\n```\n\n### What do you see instead?\n\nThe above error.\n\n### Additional information\n\n`0bf9e9f833` (#65963) introduced a regression. It destroys the duplex when an async function body resolves without consuming its input, so that `pipeline()` propagates destruction upstream. It destroys it through `destroyer()`, which synthesizes an `AbortError` for any stream that is not yet finished.\n\nThis bug breaks anything that uses `p-transform` (yeoman-environment and mem-fs).\n\nPR fix here: https://github.com/nodejs/node/pull/66243","author":{"url":"https://github.com/kethinov","@type":"Person","name":"kethinov"},"datePublished":"2026-09-27T13:27:03Z","url":"https://github.com/nodejs/node/issues/66349"}