René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"stream/iter: writevSync queues invalid chunks before throwing","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nmacOS 26.5.0\n```\n\n### Subsystem\n\nstream\n\n### What steps will reproduce the bug?\n\n```js\nimport { push } from 'stream/iter';\n\nconst { writer, readable } = push({ highWaterMark: 10 });\n\ntry {\n  writer.writevSync([1]);\n} catch (e) {\n  console.log(e.name, e.code);\n}\n\nconsole.log(await readable[Symbol.asyncIterator]().next());\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\n`writevSync([1])` should throw a Node validation error like TypeError `ERR_INVALID_ARG_TYPE`, and the invalid chunk should not be written, so the readable should remain empty/pending.\n\n### What do you see instead?\n\n```console\nTypeError undefined\n[Object: null prototype] { done: false, value: [ 1 ] }\n```\nit throws `TypeError undefined`, and the invalid value is queued.\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-07-05T01:08:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/64299/node/issues/64299"}