Creating promises in Javascript - Why You Should Know This

The Big Idea

What if your code could wait for things without getting stuck or messy?

The Scenario

Imagine you want to fetch data from the internet and then show it on your webpage. Without promises, you have to wait and check repeatedly if the data has arrived before you can use it.

The Problem

This waiting and checking manually is slow and confusing. It can cause your program to freeze or behave unpredictably because you don't know exactly when the data will be ready.

The Solution

Creating promises lets you write code that says, "When the data is ready, then do this." It handles waiting for you, so your program stays smooth and easy to understand.

Before vs After

✗ Before

fetchData(function(data) {
  processData(data);
});

✓ After

new Promise((resolve) => {
  fetchData(resolve);
}).then(processData);

What It Enables

It enables writing clear, organized code that handles tasks happening now or later without freezing your app.

Real Life Example

Think of ordering food at a restaurant: you place your order (start a promise), then wait without standing at the kitchen door, and when the food is ready, the waiter brings it to you (promise resolved).

Key Takeaways

Manual waiting for tasks is slow and confusing.

Promises let your code wait smoothly and react when ready.

This makes your programs faster and easier to read.

Practice

1. What does the resolve function do inside a JavaScript Promise?

easy

A. It pauses the promise execution.

B. It marks the promise as failed.

C. It marks the promise as successfully completed.

D. It cancels the promise.

Solution

1. Step 1: Understand the role of resolve in promises

   The resolve function is called when the asynchronous task finishes successfully.

2. Step 2: Differentiate from reject

   reject is used for failure, so resolve must mean success.

3. Final Answer:

   It marks the promise as successfully completed. -> Option C

4. Quick Check:

   resolve = success [OK]

Hint: Resolve means success, reject means failure [OK]

Common Mistakes:

• Confusing resolve with reject
• Thinking resolve cancels the promise
• Believing resolve pauses execution

2. Which of the following is the correct syntax to create a new Promise in JavaScript?

easy

A. new Promise(resolve, reject) => { }

B. Promise.new((resolve, reject) => { })

C. new Promise { resolve, reject => }

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

Solution

1. Step 1: Recall the Promise constructor syntax

   The Promise constructor takes a single function with two parameters: resolve and reject, wrapped in parentheses.

2. Step 2: Check each option for correct syntax

   new Promise((resolve, reject) => { }) correctly uses new Promise((resolve, reject) => { }). Others have syntax errors.

3. Final Answer:

   new Promise((resolve, reject) => { }) -> Option D

4. Quick Check:

   Promise syntax = new Promise((resolve, reject) => { }) [OK]

Hint: Promise needs a function with (resolve, reject) inside parentheses [OK]

Common Mistakes:

• Missing parentheses around parameters
• Using wrong keyword order
• Incorrect arrow function syntax

3. What will be the output of this code?

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

medium

A. Done

B. undefined

C. Error

D. Promise { <pending> }

Solution

1. Step 1: Understand promise resolution

   The promise calls resolve('Done'), so it completes successfully with value 'Done'.

2. Step 2: Check what then does

   then receives the resolved value and logs it, so 'Done' is printed.

3. Final Answer:

   Done -> Option A

4. Quick Check:

   Resolved value logged = Done [OK]

Hint: Resolve value appears in then callback [OK]

Common Mistakes:

• Expecting undefined instead of resolved value
• Confusing promise object with resolved output
• Thinking promise logs automatically

4. Find the error in this Promise creation code:

const p = new Promise(resolve, reject) => {
  resolve('Success');
};

medium

A. The reject function is never called.

B. Arrow function syntax is incorrect for Promise constructor.

C. Promise constructor missing the new keyword.

D. No error, code is correct.

Solution

1. Step 1: Check Promise constructor usage

   The Promise constructor requires a single function argument wrapped in parentheses.

2. Step 2: Identify arrow function syntax error

   The code uses new Promise(resolve, reject) => { } which is invalid syntax. It should be new Promise((resolve, reject) => { }).

3. Final Answer:

   Arrow function syntax is incorrect for Promise constructor. -> Option B

4. Quick Check:

   Arrow function must be inside parentheses [OK]

Hint: Promise needs one function argument wrapped in parentheses [OK]

Common Mistakes:

• Not wrapping parameters in parentheses
• Omitting new keyword (not in this case)
• Using wrong arrow function syntax

5. You want to create a Promise that waits 1 second and then resolves with 'Done'. Which code correctly does this?

hard

A. new Promise((resolve) => { setTimeout(() => resolve('Done'), 1000); })

B. new Promise(resolve => setTimeout(resolve('Done'), 1000))

C. new Promise((resolve, reject) => { resolve('Done'); setTimeout(() => {}, 1000); })

D. new Promise(() => { setTimeout(() => resolve('Done'), 1000); })

Solution

1. Step 1: Understand how to delay resolution

   Use setTimeout to delay calling resolve by 1000 ms (1 second).

2. Step 2: Check each option for correct usage

   new Promise((resolve) => { setTimeout(() => resolve('Done'), 1000); }) correctly passes a function to Promise and calls resolve('Done') inside setTimeout. new Promise(resolve => setTimeout(resolve('Done'), 1000)) calls resolve immediately. new Promise((resolve, reject) => { resolve('Done'); setTimeout(() => {}, 1000); }) resolves immediately and delays nothing. new Promise(() => { setTimeout(() => resolve('Done'), 1000); }) does not receive resolve parameter.

3. Final Answer:

   new Promise((resolve) => { setTimeout(() => resolve('Done'), 1000); }) -> Option A

4. Quick Check:

   Delay resolve with setTimeout inside Promise [OK]

Hint: Wrap resolve call inside setTimeout function [OK]

Common Mistakes:

• Calling resolve immediately instead of inside setTimeout
• Not passing resolve parameter
• Placing setTimeout outside Promise