You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: _posts/2019-08-16-going-async.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ would be terrible.
23
23
24
24
Instead, Node.js passes those sorts of actions to the underlying operating system,
25
25
which is multi-threaded, and registers a callback that will be called when the
26
-
action completes. This is the idea of the [Event Loop that is at the heart of Node.js](https://nodejs.org/uk/docs/guides/event-loop-timers-and-nexttick/).
26
+
action completes. This is the idea of the [Event Loop that is at the heart of Node.js](https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/).
27
27
28
28
To overly simplify it, you can think of it as a queue of work. Each time the Event
29
29
Loop runs, it takes the next piece of work and runs it, which may in turn cause
0 commit comments