Skip to content

doc: fix confusing language about microtask queue #23197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devsnek merged 1 commit into from
Oct 4, 2018
Merged

doc: fix confusing language about microtask queue #23197

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/api/globals.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,8 +123,8 @@ The `queueMicrotask()` method queues a microtask to invoke `callback`. If
be emitted.

In general, `queueMicrotask` is the idiomatic choice over `process.nextTick()`.
`process.nextTick()` will always run before microtasks, and so unexpected
execution order may be observed.
`process.nextTick()` will always run before the microtask queue, and so
unexpected execution order may be observed.

```js
// Here, `queueMicrotask()` is used to ensure the 'load' event is always
Expand Down