René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"stream/iter: share() does not serialize overlapping next() calls on a consumer","articleBody":"### Version\n\n26.2.0\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 { share } from 'node:stream/iter';\n\nasync function* source() {\n  yield [new TextEncoder().encode('first')];\n  yield [new TextEncoder().encode('second')];\n}\n\nconst decoder = new TextDecoder();\nconst it = share(source()).pull()[Symbol.asyncIterator]();\n\nconst p1 = it.next();\nconst p2 = it.next();\n\nconst [r1, r2] = await Promise.all([p1, p2]);\n\nconsole.log('p1:', decoder.decode(r1.value[0]));\nconsole.log('p2:', decoder.decode(r2.value[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\n```console\np1: first\np2: second\n```\n\n`p1` is the earlier `next()` call on the same async iterator, so it should resolve with the earlier chunk.\n\n### What do you see instead?\n\n```console\np1: second\np2: first\n```\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-05-21T15:12:49.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/63477/node/issues/63477"}