Environment

• Operating System: Darwin
• Node Version: v20.12.2
• Nuxt Version: 3.12.3
• CLI Version: 3.12.0
• Nitro Version: 2.9.7
• Package Manager: [email protected]
• Builder: -
• User Config: ssr, srcDir, devtools, modules, app, runtimeConfig, components, tailwindcss, typescript, compatibilityDate
• Runtime Modules: @pinia/[email protected], @vueuse/[email protected], @nuxt/[email protected], @nuxt/[email protected], @nuxtjs/[email protected]
• Build Modules: -

Reproduction

https://stackblitz.com/edit/github-ftkhvf?file=server/plugins/shutdown.ts

Describe the bug

Even if I hook to the Nitro "close" lifecycle hook using a server plugin, the code inside the hook doesn't get called when stopping the dev server (npm run dev then Ctrl C). However, if I run the production build and stop it, the hook does get called correctly.

I would expect that the close hook gets called so I can perform a graceful shutdown of my database connections and queues even on development, but for now it only seems to work on the production build.

For some reason, the next time I start the dev server, the logs from the close hook get called on startup but not on close...

Additional context

No response

Logs

No response