You Might Not Actually Need a JS Sleep Function If any of this is news to you, you should watch this excellent conference talk: What the heck is the event loop anyway?. Rather, it will continue on its way, output “Hello!” to the console, then when the request returns a couple of hundred milliseconds later, it will output the number of repos. It will not, however, wait for the request to complete. The JavaScript interpreter will encounter the fetch command and dispatch the request. This is because fetching data from an API is an asynchronous operation in JavaScript.

If you run this code, it will output “Hello!” to the screen, then the number of public repos attributed to my GitHub account. Execution goes from top to bottom.Ĭontrast that with the equivalent JavaScript version: fetch ( '' ). It then parses the response, outputs the number of public repos attributed to my GitHub account and finally prints “Hello!” to the screen. get (uri ) )Īs one might expect, this code makes a request to the GitHub API to fetch my user data.

Understanding JavaScript’s Execution Modelīefore we get going, it’s important to make sure we understand JavaScript’s execution model correctly.Ĭonsider the following Ruby code: require 'net/http' require 'json'

Node js wait 1 second