Repository navigation
Wrong example #45048
Description
This example from the documentation (https://nodejs.org/api/process.html#when-to-use-queuemicrotask-vs-processnexttick)
import { nextTick } from 'node:process';
Promise.resolve().then(() => console.log(2));
queueMicrotask(() => console.log(3));
nextTick(() => console.log(1));
// Output:
// 1
// 2
// 3doesn't work in Windows (node 16.13 and 18.11) and Ubuntu (node 18.11). Actual output is always
2
3
1This looks like a documentation bug, but any explanation for this behavior in the main module would be appreciated.
Activity
dnalborczyk commentedon Oct 18, 2022
interestingly it does work as documented when run as a
commonjsmodule, either by requiringprocessor by using the global.jasnell commentedon Oct 18, 2022
Yeah, looks like it was never tested when the mjs version was added. This is a known scheduling difference between cjs and mjs. The mjs example just needs to be updated to reflect the correct ordering. Interested in opening a PR?
dnalborczyk commentedon Oct 19, 2022
I can put up a PR for a doc fix. I wonder tho if it would be good to add an additional note or comment about the different behavior in both module systems?
jasnell commentedon Oct 19, 2022
That would be helpful yes.
parmishh commentedon Mar 2, 2023
nairihar commentedon Jan 5, 2024
Any idea when this will be fixed? @jasnell
doc: clarify cjs/esm diff in `queueMicrotask()` vs `process.nextTick()`
doc: clarify cjs/esm diff in `queueMicrotask()` vs `process.nextTick()`
doc: clarify cjs/esm diff in `queueMicrotask()` vs `process.nextTick()`
doc: clarify cjs/esm diff in `queueMicrotask()` vs `process.nextTick()`
doc: clarify cjs/esm diff in `queueMicrotask()` vs `process.nextTick()`
doc: clarify cjs/esm diff in `queueMicrotask()` vs `process.nextTick()`