Event loop overview in Javascript

Introduction

The event loop helps JavaScript run many tasks smoothly without stopping. It makes sure your code can do things like wait for clicks or timers while still running other code.

When you want to handle user clicks or keyboard input without freezing the page.

When you use timers like setTimeout or setInterval to run code later.

When you work with data from the internet and wait for it to arrive.

When you want to run small tasks one after another without blocking the page.

When you use promises to handle results that come back later.

Syntax

Javascript

// The event loop is automatic in JavaScript and has no direct syntax.
// It works behind the scenes to manage tasks and callbacks.

You don't write the event loop yourself; the JavaScript engine runs it automatically.

Understanding it helps you write code that doesn't freeze the page and handles tasks smoothly.

Examples

This shows how the event loop lets the timeout run after other code finishes.

Javascript

console.log('Start');
setTimeout(() => console.log('Timeout done'), 1000);
console.log('End');

Promises use the event loop to run their code after the current code finishes.

Javascript

console.log('First');
Promise.resolve().then(() => console.log('Promise done'));
console.log('Last');

Sample Program

This program shows that even with zero delay, the timeout callback runs after the current code because of the event loop.

Javascript

console.log('Begin');
setTimeout(() => console.log('Timeout callback'), 0);
console.log('Finish');

Important Notes

The event loop checks the task queue and runs tasks one by one after the current code.

Tasks like setTimeout callbacks and promise handlers wait in queues until the event loop runs them.

Long-running code blocks the event loop and can freeze the page, so keep tasks short.

Summary

The event loop lets JavaScript handle many tasks smoothly without stopping.

It runs code from queues after the current code finishes.

Understanding it helps you write responsive and efficient programs.

Practice

1. What is the main role of the JavaScript event loop?

easy

A. To manage execution of multiple tasks without stopping the program

B. To compile JavaScript code into machine code

C. To store variables and functions in memory

D. To style HTML elements dynamically

Solution

1. Step 1: Understand event loop purpose

   The event loop allows JavaScript to handle many tasks smoothly by managing task execution order.

2. Step 2: Compare options with event loop role

   Only To manage execution of multiple tasks without stopping the program describes managing multiple tasks without stopping, which matches the event loop's job.

3. Final Answer:

   To manage execution of multiple tasks without stopping the program -> Option A

4. Quick Check:

   Event loop = manages tasks smoothly [OK]

Hint: Event loop runs tasks one by one without freezing [OK]

Common Mistakes:

• Confusing event loop with code compilation
• Thinking event loop handles styling
• Believing event loop stores variables

2. Which of the following is the correct syntax to schedule a function to run after the current code using the event loop?

easy

A. setTimeout(myFunction, 0);

B. runLater(myFunction);

C. delay(myFunction, 0);

D. executeAfter(myFunction);

Solution

1. Step 1: Identify standard JavaScript function for scheduling

   setTimeout is the built-in function to schedule code after current execution.

2. Step 2: Check options for correct syntax

   Only setTimeout(myFunction, 0) is valid JavaScript syntax to schedule a function immediately after current code.

3. Final Answer:

   setTimeout(myFunction, 0); -> Option A

4. Quick Check:

   Use setTimeout(fn, 0) to schedule tasks [OK]

Hint: Remember setTimeout(fn, 0) delays after current code [OK]

Common Mistakes:

• Using non-existent functions like runLater or delay
• Omitting the delay argument in setTimeout
• Confusing setTimeout with synchronous calls

3. What will be the output of the following code?

console.log('Start');
setTimeout(() => console.log('Timeout'), 0);
console.log('End');

medium

A. StartTimeoutEnd

B. StartEndTimeout

C. TimeoutStartEnd

D. EndStartTimeout

Solution

1. Step 1: Understand synchronous and asynchronous order

   console.log('Start') runs first, then setTimeout schedules 'Timeout' to run later, then console.log('End') runs immediately.

2. Step 2: Determine output order

   'Start' prints, then 'End' prints, then after current code finishes, 'Timeout' prints from the event loop.

3. Final Answer:

   Start
   End
   Timeout -> Option B

4. Quick Check:

   Sync logs first, then setTimeout logs [OK]

Hint: setTimeout runs after current code finishes [OK]

Common Mistakes:

• Assuming setTimeout runs immediately
• Mixing order of synchronous logs
• Ignoring event loop delay

4. Identify the error in this code snippet related to the event loop:

setTimeout(() => {
  console.log('Hello');
}, '1000');

medium

A. setTimeout requires three arguments

B. Arrow functions cannot be used with setTimeout

C. Missing parentheses after console.log

D. The delay should be a number, not a string

Solution

1. Step 1: Check setTimeout delay argument type

   The delay argument must be a number, but here it is a string '1000'.

2. Step 2: Understand effect of wrong type

   Passing a string may cause unexpected behavior or be coerced, but best practice is to use a number.

3. Final Answer:

   The delay should be a number, not a string -> Option D

4. Quick Check:

   Delay must be number in setTimeout [OK]

Hint: Use number for delay in setTimeout, not string [OK]

Common Mistakes:

• Using string instead of number for delay
• Thinking arrow functions are invalid here
• Assuming setTimeout needs 3 arguments

5. You want to run two functions, first() and second(), so that second() runs only after first() finishes, but first() contains asynchronous code using setTimeout. How can you ensure second() runs after first() completes all its tasks?

hard

A. Use two separate setTimeout calls with the same delay

B. Call second() immediately after calling first()

C. Call second() inside the callback of setTimeout in first()

D. Use a loop to wait until first() finishes

Solution

1. Step 1: Understand asynchronous behavior of setTimeout

   setTimeout runs code later, so code after first() runs immediately without waiting.

2. Step 2: Ensure second() runs after first()'s async code

   To guarantee order, call second() inside the setTimeout callback in first(), so it runs after the async task.

3. Final Answer:

   Call second() inside the callback of setTimeout in first() -> Option C

4. Quick Check:

   Chain async calls inside callbacks to keep order [OK]

Hint: Put second() inside first()'s async callback [OK]

Common Mistakes:

• Calling second() immediately after first() ignoring async
• Using multiple setTimeouts with same delay expecting order
• Trying to block with loops instead of callbacks