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
Can be tested with the playground here (node v24.19.0):
nr dev at root (one terminal)
pnpm nuxt dev (in another terminal)
open / and navigate to /ws, then click ping button
on playground terminal press q: the process awaits the default timeout (15s) and then logs:
[nitro-runtime] close: 0.054ms
◐ Cleaning up... press Ctrl-C again to exit immediately..
WARN force closing dev worker...
◒ Cleaning up... press Ctrl-C again to exit immediately...function
│
▲ The dev server did not shut down within 15s: 80 file watchers, 1 worker thread, 1 open connection, 2 timers. Exiting anyway.
◇ Canceled
I added a hack to show the opened connections adding the following code before calling summariseActiveResources at setupSignalHandlers in dev.ts:
changed the title [-]alpha version: quit command hangs/timeout on Windows 10 PRO[/-][+]alpha version: quit command hangs/timeouts on Windows 10 PRO[/+]on Sep 10, 2026
Activity
[-]alpha version: quit command hangs/timeout on Windows 10 PRO[/-][+]alpha version: quit command hangs/timeouts on Windows 10 PRO[/+][-]alpha version: quit command hangs/timeouts on Windows 10 PRO[/-][+]alpha version: quit command hangs/timeouts[/+]