Master Hoisting in JavaScript with 5 Examples
Code snippet examples which will help to grasp the concept of Hoisting in JavaScript, with solutions to understand how it works behind the scene.
Alok Kumar Giri
Last Updated Feb 21, 2026

Understanding hoisting in JavaScript is important to understand how the variables and function scope behave in different scenarios. There are different scenarios where hoisting behaves differently than anticipated, which makes hoisting a favourite topic for Frontend Interviews.
In this post, we have curated 5 examples with detailed explanations which cover important scenarios to understand hoisting in depth. š
Jump to the examples
- Example 1: Overshadow variable
- Example 2: Hoisting with different variable types
- Example 3: Function Hoisting
- Example 4: Methods Hoisting
- Example 5: Variable hoisting with inner functions
Example 1: Overshadow variable
var foo = 'LION';
function showName(){
foo = 'PANDA';
return;
function foo(){};
};
showName(); // Guess o/p
console.log(foo); // Guess o/p
Solution:
- Memory Phase
- Execution Phase
In Memory phase
function showName(){ // Function declaration is hoisted to the top of their scope with its entire function body. Since showName() is in the global scope, it’s hoisted to the top of the global scope.
function foo(){}; // As mentioned above, it is hoisted to the top its scope. In this case, in the function scope showName() along with its entire function body. So, foo becomes the local variable of type 'function'.
foo = 'PANDA';
return;
};
var foo = undefined; // Only the declaration of 'var' is attached to the global scope with default initialization to 'undefined'.
Note: "During hoisting, JavaScript places function declarations like function showName() { ... } in memory before any var declarations, even if the var appears earlier in the source code."
In the Execution Phase
showName(); // Runs, but only changes local `foo` to PANDA
console.log(foo); // LION
Explanation:
foo(){} as hoisted to the top of its function body, will be overridden by the next line's foo variable with value 'PANDA', this foo becomes a local variable. Thus, on the console, we see 'LION' for foo.Example 2: Hoisting with different variable types
Guess the output of the code snippet below
console.log(a); // Guess o/p
console.log(b); // Guess o/p
console.log(c); // Guess o/p
var a = 10;
let b = 20;
const c = 30;
Solution:
The code will undergo two phases:
- Memory Phase
- Execution Phase
In Memory Phase
-
a(declared withvar) is hoisted and initialized toundefined. -
b(withlet) is hoisted but in TDZ(Temporal Dead Zone) (not initialized yet). -
c(withconst) is hoisted but in TDZ (not initialised yet).
In the Execution Phase
/*
Output: undefined → Because a is hoisted and initialised to undefined.
*/
console.log(a);
/*
Output: Throws ReferenceError → b is in the Temporal Dead Zone (TDZ),
so any access before declaration throws a ReferenceError.
*/
console.log(b);
/*
Never Executed as console.log(b) already throws the ReferenceError,
but if console.log(b) is commented, then this too shall throw ReferenceError → c is in the Temporal Dead Zone (TDZ).
*/
console.log(c); //
var a = 10;
let b = 20;
const c = 30;
Notes:
-
The Temporal Dead Zone is the period between: When a
letorconstvariable is hoisted to the top of its scope and when the variable is actually declared (initialized) in the code. During this time, the variable exists in memory, but you cannot access it — doing so will throw aReferenceError. - Why is it called "Dead Zone"? : Because although the variable is technically hoisted, it's in a state where it's "not alive" (usable) yet. Trying to use it before its declaration is like trying to drink from an empty cup that hasn’t even been filled yet š .
Example 3: Function Hoisting
Guess the output of the code snippet below:
greet(); // Guess the O/P
shout(); // Guess the O/P
whisper(); // Guess the O/P
function greet() {
console.log("Hello from greet()");
}
var shout = () => {
console.log("Hello from shout()");
};
let whisper = () => {
console.log("Hello from whisper()");
};
Solution:
- Memory Phase
- Execution Phase
// A function declared as a function declaration, the entire function is hoisted to the top of the scope.
greet → function() { console.log("Hello from greet()") }
// As this function is declared using 'var'
shout → undefined
// As declared using 'let'
whisper → TDZ (not initialized yet)
In the Execution Phase
/*
ā
Output: Hello from greet()
*/
greet();
/*
ā TypeError: shout is not a function →
This would NOT be hoisted the same way — only the greet variable would be hoisted as 'undefined',
not the function body. So calling greet() before this line would give you a TypeError.
*/
shout();
/*
Never Executed as shout() shall throw an error before but if shout() is commented,
then → ā ReferenceError: Cannot access 'whisper' before initialization
*/
whisper();
function greet() {
console.log("Hello from greet()");
}
var shout = () => {
console.log("Hello from shout()");
};
let whisper = () => {
console.log("Hello from whisper()");
};
Guess the output of the code snippet below:
console.log(myObjA.sayHello()); // Guess the O/p
console.log(myObjB.sayHello()); // Guess the O/p
var myObjA = {
sayHello: function () {
return "Hello!";
}
};
const myObjB = {
sayHello: function () {
return "Hello!";
}
};
Solution:
- The Memory Phase
- The Execution Phase
In Memory Creation Phase
myObjA = undefined
var myObj is hoisted and initialized with 'undefined'. Here, the object literal { sayHello: function() { ... } } is not assigned yet. Therefore, no function named sayHello exists independently in memory.
myObjB is in TDZ (Temporal Dead Zone)
const and let variables go into the Temporal Dead Zone (TDZ) — they’re not accessible until the engine reaches the declaration line.
In the Execution Phase
/*
ā TypeError: myObjA.sayHello is not a function.
When JS engine sees console.log(myObj.sayHello()),
myObjA is 'undefined' at that point (assignment hasn’t happened yet)
and thus, trying to access sayHello from undefined throws an error.
*/
console.log(myObjA.sayHello());
/*
ā ReferenceError: Cannot access 'myObjB' before initialization.
When JS engine tries to run:
*/
console.log(myObjB.sayHello());
/*
Since myObjB is still in the TDZ, a ReferenceError is thrown.
*/
console.log(myObjB.sayHello())
var myObjA = {
sayHello: function () {
return "Hello!";
}
};
const myObjB = {
sayHello: function () {
return "Hello!";
}
};
var globalVar = "I am Global";
function outerFunction() {
var outerVar = "I am Outer";
function innerFunction() {
console.log(globalVar); // Guess the O/P
console.log(outerVar); // Guess the O/P
}
innerFunction();
}
outerFunction();
Solution:
- The Memory Phase
- The Execution Phase
In Memory Creation Phase
-
globalVar is declared and initialized with 'undefined'.
outerFunctionbeing a 'function declaration' is hoisted as a complete function (its definition is available in memory)- Inside
outerFunction,outerVarandinnerFunctionare prepared in memory whenouterFunctiongets invoked (not before). outerVar→ 'undefined' initially (before outerFunction's code runs)innerFunction→ whole function stored (just like normal function hoisting inside a function).
outerFunction()is called.-
Inside
outerFunction:-
outerVaris assigned"I am Outer". -
innerFunctionis called.
-
-
Inside
innerFunction:-
It looks for
globalVar. Not found inside itself → goes to outer scopes → finds it in global → logs"I am Global". -
It looks for
outerVar. Found inouterFunction's local memory → logs"I am Outer".
-
var globalVar = "I am Global";
function outerFunction() {
var outerVar = "I am Outer";
function innerFunction() {
console.log(globalVar); // I am Global
console.log(outerVar); // I am Outer
}
innerFunction();
}
outerFunction();
ā© Next Read
Learn Next
Comments
Be the first to share your thoughts!
No comments yet.
Start the conversation!
Share your expertise
Publish a blog or quick notes on topics you know well ā your write-up could be the answer someone needs before their next frontend interview.
Build your portfolio
Help the community
Sharpen your skills
Earn goodies
Other Related Blogs
Best Frontend System Design Interview Cheat Sheet š
Anuj Sharma
Last Updated Jun 9, 2026
A Comprehensive Frontend System Design Cheat Sheet helps you approach the Frontend System Design Interview in the most structured way and covers the 7 most important Frontend System Design Topics.
React Hook Rules: Why hooks declarations are not allowed inside functions
Frontendgeek
Last Updated Feb 6, 2026
A quick guide to explain an important react interview question, why React Hooks declarations are not allowed inside functions or any conditional blocks with code example.
Implementing a stopwatch using React - Frontend Machine Coding Question
Pallavi Gupta
Last Updated Feb 21, 2026
Concise explanation of stopwatch implementation using React, it involves the usage of useEffect hook for creating a stopwatch and tracking milliseconds.
Implement useClickOutside() custom Hook in React [Interview]
Anuj Sharma
Last Updated Dec 23, 2025
Understand the implementation of useClickOutside() custom hook in react and how it can be used to implement Modal like functionality.
