Error [ERR_INTERNAL_ASSERTION]

[Beemhuse]

Version

v20.11.1

Platform

Windows

Subsystem

No response

What steps will reproduce the bug?

It happens when I start npm on a next js 14 application

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

Not often, and I don't know of any condition, but I only discovered it in this particular Next js 14 I am working with, I am using it with sanity.io, probably that could help in narrowing down what the issue could be.

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

Its all on the terminal and after the error is displayed, it still keeps on working as usual

What do you see instead?

Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues

at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1118:3)
at Timeout.internalConnectMultipleTimeout (node:net:1687:3)
at listOnTimeout (node:internal/timers:575:11)
at process.processTimers (node:internal/timers:514:7) {

code: 'ERR_INTERNAL_ASSERTION'
}

Additional information

No response

[aduh95]

Duplicate of #51354

Bug was fixed on Node.js 20.12+

[Beemhuse]

Okay, good to know, I will upgrade my node then

…

On Thu, 8 Aug 2024 at 10:07, Antoine du Hamel ***@***.***> wrote: Duplicate of #51354 <#51354> Bug was fixed on Node.js 20.12+ — Reply to this email directly, view it on GitHub <#54270 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATTVHOOKGIL23MJECEKKAJDZQOQW5AVCNFSM6AAAAABMG4FDFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZWGI4DMNRVHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>