ERR_INTERNAL_ASSERTION on Strapi

[L-Weisz]

Version

node v20.10.0

Platform

Mac OS 13.2.1 (22D68)

Subsystem

No response

What steps will reproduce the bug?

start the project in dev mode

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

90% of time, I just do
nvm use
yarn
yarn develop

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

When I do yarn develop it should build and start the project in dev mode

What do you see instead?

When I do yarn develop (should build and start in develop mode) I see an error, the trace is :

the stack trace is
[INFO] Including the following ENV variables as part of the JS bundle:
- ADMIN_PATH
- STRAPI_ADMIN_BACKEND_URL
- STRAPI_TELEMETRY_DISABLED
✔ Building build context (135ms)
✔ Creating admin (6631ms)
✔ Loading Strapi (1207ms)
✔ Generating types (310ms)
✔ Cleaning dist dir (10ms)
✔ Compiling TS (1105ms)
node:internal/assert:14
throw new ERR_INTERNAL_ASSERTION(message);
^

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'
}

Node.js v20.10.0
✨ Done in 13.40s.

Additional information

No response

[aduh95]

Duplicate of #51354