René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"stream/iter: push() replaces non-Error signal abort reasons","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nmacOS 26.5.2\n```\n\n### Subsystem\n\nstream\n\n### What steps will reproduce the bug?\n\n```js\nimport { push } from 'node:stream/iter';\n\nconst controller = new AbortController();\nconst reason = 'stop';\n\nconst { writer } = push({ signal: controller.signal });\ncontroller.abort(reason);\n\ntry {\n  await writer.write('data');\n} catch (error) {\n  console.log('same reason:', error === reason);\n  console.log('received:', `${error.name}: ${error.message}`);\n}\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\nit fails with `'stop'`, as required by [Iterable Streams §7.1, `Stream.push()`, step 12](https://stream-iter.jasnell.me/#push-method), which says to put the writer into the failed state with the signal’s abort reason.\n\n### What do you see instead?\n\n```console\nsame reason: false\nreceived: AbortError: Aborted\n```\n\nThe writer fails with a newly created `AbortError`, discarding the string abort reason.\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-07-28T04:17:52Z","url":"https://github.com/nodejs/node/issues/64797"}