You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
yarn develop
How often does it reproduce? Is there a required condition?
Often without any apparently required conditions
What is the expected behavior? Why is that the expected behavior?
enable API
What do you see instead?
yarn run v1.22.21
$ strapi develop✔ Cleaning dist dir (6ms)⠋ Building build context[INFO] Including the following ENV variables as part of the JS bundle: - ADMIN_PATH - STRAPI_ADMIN_BACKEND_URL - STRAPI_TELEMETRY_DISABLED✔ Building build context (45ms)✔ Creating admin (8206ms)✔ Loading Strapi (989ms)✔ Generating types (295ms)✔ Cleaning dist dir (19ms)✔ Compiling TS (1271ms)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 new NodeError (node:internal/errors:406:5) 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.9.0Done in 14.08s.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Version
Node.js v20.9.0
Platform
#40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
yarn develop
How often does it reproduce? Is there a required condition?
Often without any apparently required conditions
What is the expected behavior? Why is that the expected behavior?
enable API
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: