Why Hoisting with let and const in Javascript? - Purpose & Use Cases

The Big Idea

What if the way JavaScript lifts your variables silently is the secret behind your mysterious bugs?

The Scenario

Imagine you write JavaScript code and try to use a variable before you declare it. You expect it to work because you saw it happen with older code using var. But suddenly, your program crashes or behaves strangely.

The Problem

Using variables without understanding how they are lifted in the background causes bugs that are hard to find. You might spend hours wondering why your code breaks when you use let or const before declaring them, unlike var. This confusion slows you down and makes your code unreliable.

The Solution

Understanding how let and const are hoisted but stay in a 'temporal dead zone' until declared helps you write safer code. You learn to declare variables before use, avoiding unexpected errors and making your programs clearer and more predictable.

Before vs After

✗ Before

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

✓ After

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

What It Enables

Knowing hoisting rules with let and const lets you avoid tricky bugs and write clean, error-free JavaScript that runs exactly as you expect.

Real Life Example

When building interactive web pages, you often update variables based on user actions. If you accidentally use a variable before declaring it with let or const, your page might freeze or show errors. Understanding hoisting prevents this and keeps your app smooth.

Key Takeaways

Variables declared with let and const are hoisted but not initialized immediately.

Accessing them before declaration causes errors due to the temporal dead zone.

Declaring variables before use avoids confusing bugs and improves code clarity.

Practice

1. What happens if you try to access a let variable before its declaration in JavaScript?

easy

A. It returns the variable's default value.

B. It throws a ReferenceError due to the temporal dead zone.

C. It returns null.

D. It returns undefined.

Solution

1. Step 1: Understand hoisting behavior of let

   Variables declared with let are hoisted but not initialized immediately.

2. Step 2: Access before declaration causes error

   Accessing such variables before declaration triggers a ReferenceError due to the temporal dead zone.

3. Final Answer:

   It throws a ReferenceError due to the temporal dead zone. -> Option B

4. Quick Check:

   Temporal Dead Zone = ReferenceError [OK]

Hint: Accessing before declaration with let/const causes ReferenceError [OK]

Common Mistakes:

• Thinking it returns undefined like var
• Assuming it returns null
• Believing it has a default value

2. Which of the following is the correct syntax to declare a constant variable in JavaScript?

easy

A. const PI = 3.14;

B. let const PI = 3.14;

C. constant PI = 3.14;

D. var const PI = 3.14;

Solution

1. Step 1: Recall correct const declaration syntax

   The correct way to declare a constant is using const followed by the variable name and assignment.

2. Step 2: Identify invalid syntax options

   Options B, C, and D use invalid keywords or combinations not supported in JavaScript.

3. Final Answer:

   const PI = 3.14; -> Option A

4. Quick Check:

   const declaration syntax = const name = value [OK]

Hint: Use 'const name = value;' to declare constants [OK]

Common Mistakes:

• Using 'constant' keyword instead of 'const'
• Combining let or var with const
• Missing assignment during declaration

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

console.log(x);
let x = 10;

medium

A. 10

B. undefined

C. ReferenceError

D. null

Solution

1. Step 1: Analyze variable declaration and usage

   The variable x is declared with let after the console.log statement.

2. Step 2: Understand temporal dead zone effect

   Accessing x before its declaration causes a ReferenceError due to the temporal dead zone.

3. Final Answer:

   ReferenceError -> Option C

4. Quick Check:

   let before declaration = ReferenceError [OK]

Hint: Accessing let before declaration throws ReferenceError [OK]

Common Mistakes:

• Assuming it prints undefined like var
• Expecting the value 10 immediately
• Thinking it prints null

4. Identify the error in the following code and fix it:

function test() {
  console.log(a);
  const a = 5;
}
test();

medium

A. No error, outputs 5

B. TypeError, fix by initializing a with null

C. SyntaxError, fix by changing const to var

D. ReferenceError, fix by moving const declaration before console.log

Solution

1. Step 1: Identify the cause of error

   Accessing a before its const declaration causes a ReferenceError due to temporal dead zone.

2. Step 2: Fix by reordering declaration

   Moving the const a = 5; line before console.log(a); fixes the error.

3. Final Answer:

   ReferenceError, fix by moving const declaration before console.log -> Option D

4. Quick Check:

   Declare const before use to avoid ReferenceError [OK]

Hint: Declare const before use to avoid ReferenceError [OK]

Common Mistakes:

• Changing const to var without fixing order
• Ignoring temporal dead zone
• Assuming no error occurs

5. Consider the code below. What will be the output and why?

const a = 1;
{
  console.log(a);
  let a = 2;
}

hard

A. ReferenceError

B. 2

C. 1

D. undefined

Solution

1. Step 1: Understand block scope and hoisting

   The block declares a new let a which is hoisted but uninitialized inside the block.

2. Step 2: Accessing a before let a declaration

   Inside the block, console.log(a) tries to access the block-scoped a before its declaration, causing a ReferenceError due to temporal dead zone.

3. Final Answer:

   ReferenceError -> Option A

4. Quick Check:

   Block-scoped let shadows outer const causing ReferenceError [OK]

Hint: Block let shadows outer const; accessing before declaration errors [OK]

Common Mistakes:

• Assuming it prints outer const value 1
• Expecting it prints 2 before declaration
• Thinking it prints undefined