What Does setTimeout(0) Actually Do in Node.js?

What Does setTimeout(0) Actually Do in Node.js?

setTimeout(fn, 0) seems like it runs immediately, but it does not. Here is what it actually does and why it matters.

What setTimeout(0) Does

setTimeout(fn, 0) does not run fn immediately. It schedules fn to run in the timers phase of the next event loop tick, after the current stack and all microtasks (promise callbacks) complete.

Why It Does Not Run Immediately

The event loop runs one task at a time. When you call setTimeout(fn, 0), the callback goes to the timers queue. The current code finishes, then microtasks run, then the next macrotask (the timer callback) runs. It is deferred, not instant.

setTimeout(0) vs setImmediate

setImmediate runs in the check phase, right after the poll phase, while setTimeout runs in the timers phase. In most cases, setImmediate runs before setTimeout(0) on the next tick, but the exact order depends on context.

Why People Use setTimeout(0)

To defer work to the next event loop tick, letting the current stack complete and the event loop process I/O first. This is a pattern for breaking up heavy work or running code after the current operation finishes.

A Better Alternative: setImmediate

For deferring to the next tick, setImmediate is often better than setTimeout(0). It is clearer in intent and runs in the check phase, right after I/O events are processed.

The Common Misunderstanding

People think setTimeout(0) runs immediately or in parallel. It does not. It runs on the next event loop tick, after the current stack completes. Understanding this prevents bugs when you rely on timing.

The Takeaway

setTimeout(fn, 0) does not run immediately. It defers fn to the timers phase of the next event loop tick, after the current stack and all microtasks complete. For deferring to the next tick, setImmediate is often a clearer alternative.