How do I fix nodemon not restarting with Turso?

Add the signal handlers above — close tursoClient on SIGUSR2, SIGINT, SIGTERM.

Why is my Node.js server stuck on port 3000 with libSQL?

Persistent socket blocks exit; kill with `killall node` or implement graceful shutdown.

Yes, after `npx kill-port 3000`; signals fire same cross-OS.

Mid-save, your new route vanishes into a 404 abyss. Turns out, Turso's speedy sockets are silently sabotaging nodemon restarts.

DevTools Feed Apr 03, 2026 3 min read 11 views

Read in: Deutsch English Français 日本語 한국어

Turso's persistent sockets block nodemon restarts by preventing Node process exit. 𝕏
Fix with 20-line signal handler: close DB, server, then process.exit(0). 𝕏
Zombies? Kill ports manually; scales to prod deploys without issues. 𝕏

Published by

Ship faster. Build smarter.

#Node.js #express #hot reload #libsql #nodemon #turso

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to