`Response.body` is type of `PassThrough` instead of `ReadableStream` about undici HOT 4 CLOSED

PassThrough Stream is a Duplex Stream, which also implements a ReadableStream. But maybe it is not a Webstream

Does it happen when using deflate/inflate as compression?

from undici.

I don't believe there's compression happening. The transfer encoding is chunked

from undici.

Would you be able to share what dependency is using undici? It's unlikely to be an issue here.

from undici.

Aghh I've figured out the problem and it's not Undici. We utilize an api client to contact another service. Upon importing it, it checks if it's in a browser. If it's not, it overrides the global fetch to be node-fetch. Only one of the configurations causes us to use this client and we dynamically import it then. Since the tests and the service are running within the same Node instance, that means the calls to fetch() in the tests started using node-fetch's implementation after we tested that configuration. So, the order of things was basically:

• Configuration A endpoint test
  • globalThis.fetch is still Undici
  • Test passes just fine
• Configuration B endpoint test
  • globalThis.fetch is still Undici
  • Api client is imported
  • globalThis.fetch is now node-fetch
  • Test passes just fine somehow?
• Configuration C & D endpoint tests
  • globalThis.fetch is node-fetch
  • Tests fail, mocks aren't present, this issue pops up, etc.

In retrospect this probably should've been a bit more obvious to me haha 😅

Closing now, thank y'all for your assistance!

from undici.