Skip to main content

Editable event-loop - beginner

Promise vs Timer

Change timer delay and promise count to see why promise callbacks still beat timer callbacks.

partially simulatedcurated scenariodoes not execute real code
Short answer

The key output order is A -> D -> C -> B. Promise callbacks use the microtask queue, which is drained before timer tasks.

Real-world bug this helps solve

Console output or cleanup runs in an order that does not match the source code order. Promise-based state updates can happen before scheduled timers and animation cleanup.

Common wrong assumption

Treating all async callbacks as the same queue.

Fix direction

Make ordering explicit instead of relying on when a queued callback might happen to run.

Fixed code pattern
Promise.resolve().then(handleMicrotask);
setTimeout(handleTimer, 0);
// Assert/expect the microtask before the timer.
Visual proof

The console lane proves the visible order: A -> D -> C -> B. The active line and queues show why source order changed.

How to verify in a real app

Add temporary logs around the sync line, promise callback, and timer, then confirm the order without adding arbitrary delays.

Share
Loading editable case...

Related cases

Continue with nearby confusion while the mental model is fresh.

Recommended next

Was this clear?

This stays local for now. It helps you track where the product still needs sharper cases.

Send detail