TransformStream writable and writer exit prematurely

[guest271314]

Consider this code

transformstream-response-test.js

(async () => {
  try {
    let { readable, writable } = new TransformStream();
    let writer = writable.getWriter();
    new Response(readable).text().then(console.log);
    let encoder = new TextEncoder();
    console.log(readable, writable, writer);
    for (const data of "abcdef") {
      console.log({ data }); // {"data": "a"}
      await writer.ready;
      await writer.write(encoder.encode(data));
    }
    await writer.close();
    await writer.closed;
    console.log(
      "We never get here... if we comment line 4 and uncomment line 15",
    );
    // console.log(await new Response(readable).text());
  } catch (e) {
    console.error(e);
  }
})();

tjs, which still just logs

{ data: 'a' } 
[object ReadableStream]

Expected result: "abcdef"

See MattiasBuelens/web-streams-polyfill#143.

[saghul]

Thanks for reporting it upstream. I'm using that polyfill, so once it gets a fix I can bump the dependency here.

[saghul]

Looks like a limitation of the fetch polyfill we use , right @guest271314 ? Can I close this then?

[guest271314]

Looks like a limitation of the fetch polyfill we use , right @guest271314 ?

Looks like it.

Can I close this then?

Let's fix it. Implement WHATWG Streams, including Transferable Streams, and full-duplex streaming.

[saghul]

That might be a bit of a tall order, but we might get there. As usual, patches are more than welcome!

[guest271314]

@saghul deno and node implement full-duplex streaming and processing upload streaming. I know what the implementation should look like. Might nt be today or tomorrow when we get this working. We should strive for excellence, no matter how long it takes to get there.