Why What hoisting is in Javascript? - Purpose & Use Cases

The Big Idea

Ever wondered why JavaScript lets you use variables before you declare them? The secret is hoisting!

The Scenario

Imagine you write a JavaScript program where you try to use a variable or function before you actually write it down in your code. You might expect the program to stop and tell you it doesn't know what you mean. But sometimes, it doesn't behave that way, which can be confusing.

The Problem

Without understanding hoisting, you might spend a lot of time debugging why your code runs strangely or why variables seem to exist before you declare them. This can make your code unpredictable and hard to fix, especially when you expect things to happen in the order you wrote them.

The Solution

Hoisting is JavaScript's way of moving variable and function declarations to the top of their scope before running the code. This means you can use functions and some variables before you write them down, making the code run without errors but sometimes causing confusion if you don't know about it.

Before vs After

✗ Before

console.log(x);
var x = 5;

✓ After

var x = 5;
console.log(x);

What It Enables

Understanding hoisting helps you write clearer code and avoid unexpected bugs by knowing how JavaScript treats your variables and functions behind the scenes.

Real Life Example

Think of hoisting like packing for a trip: you put all your essentials at the top of your suitcase so you can find them quickly, even if you packed them later. Similarly, JavaScript 'packs' declarations at the top so it can find them when running your code.

Key Takeaways

Hoisting moves declarations to the top before code runs.

It allows using functions and variables before they appear in code.

Knowing hoisting prevents confusing bugs and helps write better code.

Practice

1. What does hoisting mean in JavaScript?

easy

A. JavaScript converts all variables to global scope automatically.

B. JavaScript moves variable and function declarations to the top before running code.

C. JavaScript delays execution of code until user interaction.

D. JavaScript runs code only after the entire file is loaded.

Solution

1. Step 1: Understand hoisting concept

   Hoisting means JavaScript moves declarations of variables and functions to the top of their scope before running the code.

2. Step 2: Compare options

   Only JavaScript moves variable and function declarations to the top before running code. correctly describes this behavior. Other options describe unrelated behaviors.

3. Final Answer:

   JavaScript moves variable and function declarations to the top before running code. -> Option B

4. Quick Check:

   Hoisting = Moving declarations up [OK]

Hint: Hoisting means declarations move up before code runs [OK]

Common Mistakes:

• Thinking hoisting moves variable assignments, not just declarations
• Confusing hoisting with asynchronous code execution
• Believing hoisting applies to all variable types equally

2. Which of the following variable declarations is hoisted and initialized as undefined?

easy

A. function foo() {}

B. const y = 10;

C. let x = 5;

D. var z = 15;

Solution

1. Step 1: Identify hoisting behavior for variable types

   Variables declared with var are hoisted and initialized as undefined. let and const are hoisted but not initialized, causing a temporal dead zone.

2. Step 2: Match options to behavior

   var z = 15; uses var, so it is hoisted and initialized as undefined. Others do not behave this way.

3. Final Answer:

   var z = 15; -> Option D

4. Quick Check:

   var hoisted as undefined [OK]

Hint: Only var variables are hoisted and set to undefined [OK]

Common Mistakes:

• Assuming let and const behave like var with hoisting
• Confusing function declarations with variable declarations
• Thinking function expressions are hoisted like functions

3. What will be the output of this code?

console.log(myVar);
var myVar = 10;

medium

A. undefined

B. 10

C. ReferenceError

D. null

Solution

1. Step 1: Understand var hoisting with initialization

   The declaration var myVar is hoisted to the top, but the assignment = 10 stays in place.

2. Step 2: Evaluate console.log output

   At the time of console.log(myVar), myVar exists but is undefined because assignment hasn't happened yet.

3. Final Answer:

   undefined -> Option A

4. Quick Check:

   var declaration hoisted, value undefined [OK]

Hint: var declaration hoisted, value assigned later [OK]

Common Mistakes:

• Expecting the value 10 to print immediately
• Confusing ReferenceError with undefined for var
• Thinking let or const behave the same way

4. Find the error in this code related to hoisting:

console.log(foo());
var foo = function() { return 'Hello'; };

medium

A. No error, outputs 'Hello'

B. SyntaxError

C. TypeError: foo is not a function

D. ReferenceError: foo is not defined

Solution

1. Step 1: Understand hoisting of function expressions

   Variable foo is hoisted as undefined, but the function assignment is not hoisted.

2. Step 2: Analyze calling foo before assignment

   Calling foo() before assignment tries to call undefined as a function, causing a TypeError.

3. Final Answer:

   TypeError: foo is not a function -> Option C

4. Quick Check:

   Function expressions not hoisted as functions [OK]

Hint: Function expressions hoisted as undefined, not callable [OK]

Common Mistakes:

• Thinking function expressions are fully hoisted
• Expecting no error because of hoisting
• Confusing ReferenceError with TypeError

5. Consider this code:

console.log(greet());

function greet() {
  return 'Hi!';
}

var greet = function() {
  return 'Hello!';
};

console.log(greet());

What will be the output?

hard

A. 'Hi!' then ReferenceError

B. 'Hello!' then 'Hello!'

C. ReferenceError then 'Hello!'

D. 'Hi!' then 'Hello!'

Solution

1. Step 1: Analyze hoisting of function declaration

   The function declaration function greet() is fully hoisted, so the first greet() call returns 'Hi!'.

2. Step 2: Analyze var assignment after first call

   The var greet declaration is hoisted but initialized as undefined. The assignment to a function expression happens after the first call, so the second greet() call uses the new function returning 'Hello!'.

3. Final Answer:

   'Hi!' then ReferenceError -> Option A

4. Quick Check:

   Function declaration hoisted, var assignment overrides later [OK]

Hint: Function declarations hoisted fully; var assignments override later [OK]

Common Mistakes:

• Thinking var assignment overrides before first call
• Expecting ReferenceError due to var redeclaration
• Confusing function declaration and expression hoisting