What does queueMicrotask() do, and how does its callback ordering compare to a resolved Promise .then() and setTimeout(fn, 0)?

Q: What does queueMicrotask() do, and how does its callback ordering compare to a resolved Promise .then() and setTimeout(fn, 0)?

**Target Audience:** Engineers preparing for JavaScript event loop and async-ordering interview questions. **Difficulty:** Medium > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text. ## 1. Why This Even Matters — A Story First Picture a barista mid-pour on a drink. Right next to the register sits a small stack of quick must-do-now tickets -- restock a napkin holder, wipe a counter, hand back a card. Those get cleared immediately, one after another, the instant the current drink is finished, before the barista even looks at the next full order ticket from a table. `queueMicrotask()` and Promise `.then()` callbacks are exactly those quick tickets. A brand-new full order ticket is what `setTimeout(fn, 0)` schedules -- it only gets picked up once every single quick ticket at the regis

The problem

Question presented to candidate: "Say I call queueMicrotask, then Promise.resolve().then, then setTimeout with a delay of 0, in that exact order. What order do the three callbacks actually run in, and why?"

What a strong answer should cover:

queueMicrotask() schedules a callback on the SAME microtask queue that Promise .then callbacks use -- it is not a separate, lower-priority queue.
setTimeout(fn, 0) schedules a macrotask, which never runs until the current microtask queue is completely empty, no matter how many more microtasks get added along the way.
Ordering among microtasks follows scheduling order (FIFO), not API identity -- whichever of queueMicrotask or .then was scheduled first runs first.
A microtask that itself schedules another microtask (including a nested queueMicrotask call) still runs before the next macrotask, because the engine keeps draining the microtask queue until it is genuinely empty.
Real motivation for queueMicrotask existing: it lets code schedule microtask-timed work without allocating a throwaway Promise just to get access to .then.

Clarifying questions expected:

"Is this the browser event loop or the Node.js event loop specifically -- Node has an extra process.nextTick queue that runs even earlier than both."

Code / implementation expected: Yes -- a short, runnable snippet demonstrating the actual print order.

event-loop
microtask
queuemicrotask

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for JavaScript event loop and async-ordering interview questions. Difficulty: Medium

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text.

1. Why This Even Matters — A Story First

Picture a barista mid-pour on a drink. Right next to the register sits a small stack of quick must-do-now tickets -- restock a napkin holder, wipe a counter, hand back a card. Those get cleared immediately, one after another, the instant the current drink is finished, before the barista even looks at the next full order ticket from a table. queueMicrotask() and Promise .then() callbacks are exactly those quick tickets. A brand-new full order ticket is what `setTimeout(

The solution is hidden so you can try first

8 min read · 9 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

JavaScriptMicrotask vs macrotask ordering, including a nested microtask (run directly)