Why Nodemon Zombies Haunt Your Turso Setup (And How to Kill Them)
Your Turso database client is keeping your old server alive. Nodemon can't restart it. Here's the surgical fix that actually works.
⚡ Key Takeaways
- Turso's persistent socket connection prevents Node.js from exiting when nodemon tries to restart—the old process becomes a 'zombie' holding your port 𝕏
- Capture SIGUSR2 (nodemon restart signal) with process event handlers that explicitly close the database connection before shutdown 𝕏
- Graceful shutdown isn't optional developer niceties—it's essential infrastructure for both local development and production reliability 𝕏
Worth sharing?
Get the best Open Source stories of the week in your inbox — no noise, no spam.
Originally reported by Dev.to