Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Understanding Async JS
Lesson Plan
  1. Introduction
    1. What is Asynchronous JS?
    2. Callbacks are not automatically asynchronous
    3. What is an API?
    4. Evolution of HTTP APIs
    5. Ajax vs Asynchronous JavaScript
  2. Fundamental Concepts
    1. How to fetch resources
    2. Using XHR
    3. Using the Fetch API
    4. Using libraries
    5. Core JavaScript concepts
    6. Understanding Promises
    7. Understanding Async Functions
    8. Understanding the Event Loop
    9. Understanding JSON
    10. Async JS Best Practices
    11. Using Optimistic UI
  3. Understanding Rest API
    1. Diving into Rest APIs
    2. The Rest Architecture
    3. The Rest Structure
    4. Anatomy of a Request
    5. What's an endpoint
    6. Request methods
    7. Understanding request headers
    8. Understanding the request body
    9. Authentication
    10. Basic Authentication
    11. Bearer Authentication
    12. Authenticating with API keys and API Secrets
    13. Cross Origin Resource Sharing
    14. Anatomy of a response
    15. HTTP Statuses
    16. Response headers
    17. The response body
    18. Handling Errors
    19. Reading API documentations
    20. Understanding Curl
  4. Node Basics
    1. Why we are using Node
    2. Command Line Basics
    3. Installing Node
    4. Managing dependencies
    5. Using ES Modules in Node
    6. Using Node
    7. Restarting the server automatically
    8. Sending requests via Node
    9. Protecting API keys and secrets
  5. Building a server
    1. What's a server
    2. Building a simple server with Express
    3. Two kinds of servers
    4. API Server architecture
    5. Handling routes
    6. Understanding Middlewares
    7. Enabling CORS
    8. Receiving data
    9. Sending responses
    10. Handling errors in Express
    11. Using the server as a proxy
    12. Minimum viable server
  6. Open Authorization
    1. Open Authorisation (OAuth)
    2. Authenticating with Access Tokens
    3. Obtaining Access Tokens
    4. Public and Confidential Clients
    5. Authorisation Code Grant
    6. Understanding scope
    7. Proof Key for Code Exchange (PKCE)
    8. PKCE with Twitter
    9. Dynamic state and `code_verifier`
    10. Saving the access token in cookies
    11. Passing access tokens to the browser
    12. Saving the access token in local storage
    13. Refresh Token Grant
    14. Device Code Grant
    15. Client libraries vs REST
  7. Building Social Media Logins
    1. Introduction
    2. Starter Files
    3. Creating SSL certificates
    4. Login in with Github
    5. Github: Saving the token to local storage
    6. Github: Persisting the login status
    7. Login with Twitter
    8. Twitter: Saving the token to local storage
    9. Twitter: Persisting the login status
    10. Twitter: Refreshing the access token
    11. Login with Facebook
    12. Facebook: Saving the token to localStorage
    13. Facebook: Persisting the login status
    14. Facebook: Refreshing the access token
    15. Login with google
    16. Google: Saving the token to localStorage
    17. Google: Refreshing the access token

Using the Fetch API

1m:55s

To use Fetch, you also need to be able to do two things:

  1. Send a request with XHR
  2. Receive a response with XHR

This process is a lot faster and easier compared to XHR.

Sending a request

To send a request, you just need to pass in a url (the endpoint) into fetch.

You can then pass in any options into fetch as a second variable. These options are, well, optional.

fetch('http://link-to-resource', options)
Note

We’ll talk about what these options are later. For now, just follow along to get a rough understanding of the process.

If you want to get a list of my repositories from GitHub, you can use the following endpoint.

fetch('https://api.github.com/users/zellwk/repos')

Receiving a response

To receive a response, you add a then method after fetch.

This then method receives the response from the API server.

fetch('https://api.github.com/users/zellwk/repos')
.then(response => {
console.log(response)
})

The body property contains the data we want.

In this case, the body is a ReadableStream. (Click on the three dots and they’ll be replaced with ReadableStream).

Fetch is a readable stream

Now, you don’t have to understand what a ReadableStream is to be able to use the response from the Fetch API.

You just need to know two things:

  1. What is the type of data being sent back
  2. How to convert that data back into JavaScript

In this case, GitHub sends JSON data back to us.

To convert JSON data into a JavaScript object in the Fetch API, we need to use the response.json method.

fetch('https://api.github.com/users/zellwk/repos').then(response =>
response.json(),
)

Once you do this, you can get the data in the next then method.

fetch('https://api.github.com/users/zellwk/repos')
.then(response => response.json())
.then(data => {
console.log(data)
// Do something with the data
})

Wrapping Up

Here’s the full code you need to fetch a resource with the Fetch API.

fetch('https://api.github.com/users/zellwk/repos')
.then(response => response.json())
.then(data => {
console.log(data)
// Do something with the data
})

As you can see, it’s much simpler compared to the XHR variant. This is why people prefer raw Fetch over raw XHR.

That said, we can make things even easier with libraries.