Skip to content

docs(asynchronous-work): clarify setTimeout() scheduling in process.nextTick guide #98

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

Open
Akankshaaaa-01 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs(asynchronous-work): clarify setTimeout() scheduling in process.nextTick guide #98

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d966ad8
fix: typo "Contibute" → "Contribute" in navigation
Akankshaaaa-01 Jun 26, 2026
501a592
docs(asynchronous-work): clarify setTimeout() wording
Akankshaaaa-01 Jun 26, 2026
ac4fb26
Merge branch 'main' into docs/process-nexttick-wording
Akankshaaaa-01 Jun 26, 2026
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
2 changes: 1 addition & 1 deletion pages/asynchronous-work/understanding-processnexttick.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ The event loop is busy processing the current function code. When this operation

It's the way we can tell the JS engine to process a function asynchronously (after the current function), but as soon as possible, not queue it.

Calling `setTimeout(() => {}, 0)` will execute the function at the end of next tick, much later than when using `nextTick()` which prioritizes the call and executes it just before the beginning of the next tick.
Calling `setTimeout(() => {}, 0)` schedules the callback for a future event loop iteration, much later than when using `process.nextTick()`, which executes before the event loop continues.

Use `nextTick()` when you want to make sure that in the next event loop iteration that code is already executed.

Expand Down