Promises for cleaner async in Node.js - Mini Project: Build & Apply

Promises for cleaner async

📖 Scenario: You are building a small Node.js app that fetches user data and their posts from a server. Instead of using nested callbacks, you want to use Promises to keep your code clean and easy to read.

🎯 Goal: Build a simple Node.js script that uses Promises to fetch user data and posts asynchronously, then logs the combined result.

📋 What You'll Learn

Create a function that returns a Promise resolving user data

Create a function that returns a Promise resolving posts data

Use a configuration variable to simulate a delay time

Chain Promises to fetch user data first, then posts

Log the combined user and posts data after both Promises resolve

💡 Why This Matters

🌍 Real World

Using Promises is common in Node.js apps to handle asynchronous tasks like fetching data from APIs or databases without blocking the program.

💼 Career

Understanding Promises is essential for backend developers working with Node.js to write clean, maintainable asynchronous code.

1

Create user data fetch function

Create a function called fetchUser that returns a Promise resolving to the object { id: 1, name: 'Alice' } after a delay of 100 milliseconds.

Node.js

# Your code here

Hint

Use new Promise and setTimeout to simulate async fetching.

2

Add delay configuration variable

Create a constant called delay and set it to 150 to use as the delay time for fetching posts.

Node.js

function fetchUser() {
    return new Promise((resolve) => {
        setTimeout(() => {
            resolve({ id: 1, name: 'Alice' });
        }, 100);
    });
}

# Your code here

Hint

Use const delay = 150; to set the delay time.

3

Create posts data fetch function using delay

Create a function called fetchPosts that returns a Promise resolving to the array [{ id: 101, title: 'Post 1' }, { id: 102, title: 'Post 2' }] after a delay using the delay constant.

Node.js

function fetchUser() {
    return new Promise((resolve) => {
        setTimeout(() => {
            resolve({ id: 1, name: 'Alice' });
        }, 100);
    });
}

const delay = 150;

# Your code here

Hint

Use the delay constant inside setTimeout for the posts fetch delay.

4

Chain Promises and log combined data

Use fetchUser() and chain it with fetchPosts() using .then(). Inside the second .then(), log an object with keys user and posts containing the resolved data.

Node.js

function fetchUser() {
    return new Promise((resolve) => {
        setTimeout(() => {
            resolve({ id: 1, name: 'Alice' });
        }, 100);
    });
}

const delay = 150;

function fetchPosts() {
    return new Promise((resolve) => {
        setTimeout(() => {
            resolve([
                { id: 101, title: 'Post 1' },
                { id: 102, title: 'Post 2' }
            ]);
        }, delay);
    });
}

# Your code here

Hint

Chain fetchUser() and fetchPosts() with .then() and combine results in an object.

Practice

1. What is the main purpose of using Promises in Node.js?

easy

A. To store data permanently on disk

B. To make the program run faster by using multiple CPUs

C. To write synchronous code only

D. To handle asynchronous tasks without freezing the program

Solution

1. Step 1: Understand asynchronous tasks

   Asynchronous tasks take time and can block the program if not handled properly.

2. Step 2: Role of Promises

   Promises allow handling these tasks without freezing the program by running code after the task finishes.

3. Final Answer:

   To handle asynchronous tasks without freezing the program -> Option D

4. Quick Check:

   Promises manage async tasks = A [OK]

Hint: Promises help avoid freezing during slow tasks [OK]

Common Mistakes:

• Thinking Promises speed up code execution
• Confusing Promises with synchronous code
• Believing Promises store data permanently

2. Which of the following is the correct way to create a Promise in Node.js?

easy

A. const p = Promise(() => { resolve(); });

B. const p = new Promise((resolve, reject) => { /* code */ });

C. const p = new Promise(resolve, reject);

D. const p = Promise.new((resolve, reject) => { });

Solution

1. Step 1: Check Promise constructor syntax

   The Promise constructor requires a function with two parameters: resolve and reject.

2. Step 2: Validate each option

   const p = new Promise((resolve, reject) => { /* code */ }); correctly uses new Promise with a function taking resolve and reject.

3. Final Answer:

   const p = new Promise((resolve, reject) => { /* code */ }); -> Option B

4. Quick Check:

   Correct Promise syntax = B [OK]

Hint: Use 'new Promise' with (resolve, reject) function [OK]

Common Mistakes:

• Omitting 'new' keyword
• Passing resolve and reject outside a function
• Using incorrect Promise constructor syntax

3. What will the following code output?

const promise = new Promise((resolve) => {
  setTimeout(() => resolve('Done'), 100);
});
promise.then(result => console.log(result));
console.log('Start');

medium

A. Start only

B. Done\nStart

C. Start\nDone

D. Done only

Solution

1. Step 1: Understand asynchronous setTimeout

   The setTimeout delays resolve by 100ms, so 'Done' logs after delay.

2. Step 2: Order of console logs

   'Start' logs immediately, then after 100ms 'Done' logs from the promise.

3. Final Answer:

   Start\nDone -> Option C

4. Quick Check:

   Async delay means 'Start' first, then 'Done' [OK]

Hint: Immediate logs appear before delayed Promise results [OK]

Common Mistakes:

• Assuming Promise resolves immediately
• Expecting 'Done' before 'Start'
• Ignoring asynchronous behavior of setTimeout

4. Identify the error in this Promise code:

const p = new Promise((resolve, reject) => {
  resolve('Success');
  reject('Error');
});
p.then(result => console.log(result))
 .catch(error => console.log(error));

medium

A. Calling reject after resolve has no effect

B. Missing catch block for errors

C. Promise constructor missing 'new' keyword

D. resolve and reject parameters are reversed

Solution

1. Step 1: Understand Promise state changes

   Once a Promise is resolved or rejected, further calls to resolve or reject are ignored.

2. Step 2: Analyze code behavior

   The code calls resolve first, so reject after that does nothing.

3. Final Answer:

   Calling reject after resolve has no effect -> Option A

4. Quick Check:

   Promise settles once; later calls ignored [OK]

Hint: Promise settles once; ignore calls after resolve/reject [OK]

Common Mistakes:

• Expecting both resolve and reject to run
• Forgetting Promise settles only once
• Confusing order of resolve and reject calls

5. You want to run two async tasks one after another using Promises. Which code correctly chains them to run sequentially?

hard

A. task1().then(() => task2()).then(result => console.log(result));

B. Promise.all([task1(), task2()]).then(results => console.log(results));

C. task1(); task2(); console.log('Done');

D. task1().catch(() => task2()).then(result => console.log(result));

Solution

1. Step 1: Understand sequential chaining

   To run tasks one after another, call the second in the first's .then() callback.

2. Step 2: Analyze options

   task1().then(() => task2()).then(result => console.log(result)); chains task2 after task1 completes, ensuring order.

3. Final Answer:

   task1().then(() => task2()).then(result => console.log(result)); -> Option A

4. Quick Check:

   Chain with .then() for sequential async tasks [OK]

Hint: Use .then() chaining to run tasks one after another [OK]

Common Mistakes:

• Using Promise.all for sequential tasks (runs parallel)
• Calling tasks without chaining (runs parallel)
• Misusing catch to run second task