Why async and await are needed in Javascript - Visual Breakdown

Concept Flow - Why async and await are needed

Start

↓

Call async function

↓

Function returns Promise

↓

Use await to pause

↓

Wait for Promise to resolve

↓

Resume with resolved value

↓

Continue execution

↓

End

This flow shows how async functions return promises and await pauses execution until the promise resolves, making asynchronous code easier to write and read.

Execution Sample

Javascript

async function fetchData() {
  let data = await fetch('url');
  console.log('Data received');
}
fetchData();

This code fetches data asynchronously, waiting for the fetch to complete before logging.

Execution Table

Step	Action	Evaluation	Result
1	Call fetchData()	Returns Promise	Promise pending
2	Inside fetchData(), await fetch('url')	Pause until fetch resolves	Execution paused
3	Fetch resolves	Promise fulfilled with response	Response object
4	Resume fetchData()	Assign response to data	data = Response
5	console.log('Data received')	Print message	Output: Data received
6	fetchData() completes	Promise resolved	Execution ends

💡 fetchData() finishes after awaiting fetch and logging message

Variable Tracker

Variable	Start	After Step 4	Final
data	undefined	Response object	Response object

Key Moments - 2 Insights

Why does fetchData() return immediately even though it uses await?

Because async functions always return a Promise immediately (see Step 1), and await pauses only inside the async function without blocking the whole program.

What happens during the await fetch('url') line?

Execution inside fetchData pauses (Step 2) until the fetch Promise resolves (Step 3), then resumes with the resolved value assigned to data (Step 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the state of fetchData() right after Step 1?

A It returned a pending Promise

B It is paused at await

C It has completed execution

D It threw an error

💡 Hint

Check Step 1 in the execution_table where fetchData() returns a Promise pending

At which step does the program resume execution after waiting for fetch to complete?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at Step 4 where execution resumes and data is assigned

If we remove await, what changes in the execution table?

A fetchData() would not return a Promise

B Execution would not pause and data would be a Promise

C console.log would never run

D fetch would run synchronously

💡 Hint

Without await, data gets the Promise immediately, so no pause (compare Step 2 and 4)

Concept Snapshot

async functions always return a Promise.
await pauses execution inside async functions until the Promise resolves.
This makes asynchronous code easier to write and read.
Without await, Promises must be handled with .then() callbacks.
Using async/await avoids nested callbacks and improves clarity.

Full Transcript

This visual trace shows why async and await are needed in JavaScript. When calling an async function, it immediately returns a Promise (Step 1). Inside the async function, await pauses execution until the Promise resolves (Steps 2 and 3). Then execution resumes with the resolved value (Step 4), allowing sequential style code for asynchronous operations. This avoids complex callback chains and makes code easier to understand and maintain.

Practice

1. Why do we use async and await in JavaScript?

easy

A. To make the code run faster by skipping steps

B. To handle slow tasks without freezing the program

C. To write code that only works in old browsers

D. To stop the program completely until a task finishes

Solution

1. Step 1: Understand the problem with slow tasks

   Slow tasks like fetching data can freeze the program if handled synchronously.

2. Step 2: Role of async and await

   Async and await let the program wait for slow tasks without freezing, keeping it smooth.

3. Final Answer:

   To handle slow tasks without freezing the program -> Option B

4. Quick Check:

   Async/await = smooth waiting [OK]

Hint: Async/await = smooth waiting without freezing [OK]

Common Mistakes:

• Thinking async/await makes code faster
• Believing async/await stops the whole program
• Confusing async/await with old browser code

2. Which of the following is the correct way to declare an async function in JavaScript?

easy

A. function async fetchData() {}

B. function fetchData() async {}

C. async function fetchData() {}

D. function fetchData async() {}

Solution

1. Step 1: Recall async function syntax

   The correct syntax places async before the function keyword.

2. Step 2: Check each option

   Only async function fetchData() {} correctly uses async function fetchData() {}.

3. Final Answer:

   async function fetchData() {} -> Option C

4. Quick Check:

   Async before function keyword [OK]

Hint: Async keyword goes before function name [OK]

Common Mistakes:

• Placing async after function name
• Adding async inside function parentheses
• Writing async after function body

3. What will be the output of this code?

async function greet() {
  return 'Hello';
}

greet().then(console.log);

medium

A. 'Hello'

B. Promise { 'Hello' }

C. undefined

D. Error: greet is not a function

Solution

1. Step 1: Understand async function return

   An async function returns a Promise that resolves to the returned value.

2. Step 2: Using .then to get value

   The .then(console.log) prints the resolved value 'Hello'.

3. Final Answer:

   'Hello' -> Option A

4. Quick Check:

   Async function returns Promise, .then logs value [OK]

Hint: Async returns Promise; .then gets resolved value [OK]

Common Mistakes:

• Expecting direct string without .then
• Confusing Promise object with string
• Thinking async function returns undefined

4. Find the error in this code:

async function fetchData() {
  const data = await fetch('https://api.example.com');
  return data.json();
}

const result = fetchData();
console.log(result);

medium

A. data.json() is not a function

B. fetchData() should not be async

C. Cannot use await inside async function

D. Missing await before fetchData() call

Solution

1. Step 1: Check fetchData() call

   fetchData() returns a Promise, so logging it directly shows a Promise object.

2. Step 2: Fix by awaiting fetchData()

   Adding await before fetchData() inside an async context gets the resolved data.

3. Final Answer:

   Missing await before fetchData() call -> Option D

4. Quick Check:

   Await needed to get Promise result [OK]

Hint: Await async calls to get actual result [OK]

Common Mistakes:

• Logging Promise instead of awaited value
• Removing async keyword incorrectly
• Misunderstanding data.json() usage

5. You want to fetch user data and then fetch posts by that user. Which code correctly uses async/await to do this step-by-step without freezing the program?

function getUser() {
  return fetch('/user').then(res => res.json());
}

function getPosts(userId) {
  return fetch(`/posts?user=${userId}`).then(res => res.json());
}

// Fill in the blanks
async function loadData() {
  const user = _____ getUser();
  const posts = _____ getPosts(user.id);
  console.log(posts);
}

hard

A. await, await

B. await, then

C. then, await

D. then, then

Solution

1. Step 1: Understand async function usage

   Inside async functions, use await to wait for Promises step-by-step.

2. Step 2: Apply await to both calls

   Both getUser() and getPosts() return Promises, so both need await.

3. Final Answer:

   await, await -> Option A

4. Quick Check:

   Use await for sequential async calls [OK]

Hint: Use await for each async call inside async function [OK]

Common Mistakes:

• Mixing then and await inside async function
• Forgetting await causing Promise logs
• Using then without returning inside async