(node:6812) Warning: An error event has already been emitted on the socket. Please use the destroy method on the socket while handling a 'clientError' event. (Use node --trace-warnings ... to show where the warning was created)

[slaetthult]

Version

node v20.11.0 (npm v10.2.4)

Platform

Darwin Marvins-MBP.localdomain 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10 PST 2023; root:xnu-10002.61.3~2/RELEASE_X86_64 x86_64

Subsystem

No response

What steps will reproduce the bug?

Astro 4 npm run dev

How often does it reproduce? Is there a required condition?

Every time npm run dev

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

(node:6812) Warning: An error event has already been emitted on the socket. Please use the destroy method on the socket while handling a 'clientError' event. (Use node --trace-warnings ... to show where the warning was created)

Additional information

No response

[marco-ippolito]

@slaetthult hello, thanks for reporting the issue, you can use node --trace-warnings to check where the warning is generated.
If you think this is a bug within Node.js can you provide a repro?
Otherwise I think you should open an issue on Astro rather than on Node.js @ematipico

[slaetthult]

@marco-ippolito when i use node --trace-warnings i get the following:
(node:26244) Warning: An error event has already been emitted on the socket. Please use the destroy method on the socket while handling a 'clientError' event.
at warnUnclosedSocket (node:_http_server:866:11)
at Socket.socketOnError (node:_http_server:880:5)
at onParserExecuteCommon (node:_http_server:915:19)
at onParserExecute (node:_http_server:836:3)

[marco-ippolito]

this warning has been removed in #51204, the fix will be released in a future version