Skip to content

Commit 83081ef

Browse files
authored
content: clarify process.nextTick() timing (#7204)
1 parent d67507e commit 83081ef

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

apps/site/pages/en/learn/asynchronous-work/understanding-processnexttick.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,10 @@ authors: flaviocopes, MylesBorins, LaRuaNa, ahmadawais, ovflowd, marksist300
66

77
# Understanding process.nextTick()
88

9-
As you try to understand the Node.js event loop, one important part of it is `process.nextTick()`. Every time the event loop takes a full trip, we call it a tick.
9+
As you try to understand the Node.js event loop, one important part of it is `process.nextTick()`.
10+
Every time the runtime calls back into JavaScript for an event, we call it a tick.
1011

11-
When we pass a function to `process.nextTick()`, we instruct the engine to invoke this function at the end of the current operation, before the next event loop tick starts:
12+
When we pass a function to `process.nextTick()`, we instruct the engine to invoke this function immediately after the current operation completes, before moving to the next phase in the event loop:
1213

1314
```js
1415
process.nextTick(() => {

0 commit comments

Comments
 (0)