An error in the response body should destroy the response stream in Node

[gmaclennan]

Describe the bug

If a response body stream is aborted or errors, the node response stream should be destroyed and the socket closed. Currently an error in the response body stream results in an unhandled error and does not close the socket.

To Reproduce Steps to reproduce the behavior:

Abort or create an error in a stream that has been sent as a response body when using the node handler.

Expected behavior

The reponse stream should be closed and the client should see and RST ECONNRESET.

Environment:

• OS: MacOS
• @whatwg-node/server
• NodeJS: v22.20.0

Additional context

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• ReadableStream pipeTo() should throw on error #3003

Related Issues

• setResponse in ServerAdapter onResponseHook is not reflected in subsequent hooks #2053
• CustomAbortControllerSignal should not use max listeners limit #2451
• CustomAbortControllerSignal doesn't fit to AbortSignal.any #2445
• normalizeNodeRequest strips some properties from Koa server "Request" object #2044

🔗 Related PRs

#2643 - Fix response stream cancellation via break; in the for await loop [merged]

👤 Suggested Assignees

• slagiewka
• gmaclennan
• sonewman
• aryascripts
• ardatan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[ardatan]

Could you share a reproduction with a PR by any chance? Thanks!