JavaScript Hoisting Variable Undefined Fix

In this tutorial, you'll learn about JavaScript Hoisting Variable Undefined Fix. We cover key concepts, practical examples, and best practices.

The Problem

JavaScript hoisting moves variable and function declarations to the top of their scope before execution. Variables declared with var are hoisted and initialized as undefined, while let and const are hoisted but not initialized — creating a temporal dead zone that throws ReferenceError.

Quick Fix

Step 1: Understand var hoisting

// Wrong — reads undefined before assignment
console.log(value); // undefined
var value = 5;
console.log(value); // 5

// The above is interpreted as:
var value;
console.log(value); // undefined
value = 5;
console.log(value); // 5

Step 2: Fix temporal dead zone with let/const

// Wrong — ReferenceError: Cannot access before initialization
console.log(name); // ReferenceError
let name = 'Alice';

// Right — declare before use
let name = 'Alice';
console.log(name); // Alice

Step 3: Function declarations are fully hoisted

// Works — function declarations hoist completely
sayHello(); // Hello!

function sayHello() {
    console.log('Hello!');
}

// Wrong — function expressions only hoist the variable
sayHi(); // TypeError: sayHi is not a function
var sayHi = function() {
    console.log('Hi!');
};

Step 4: Avoid hoisting confusion with function expressions vs declarations

// Hoisted — works before definition
console.log(double(5)); // 10

function double(n) {
    return n * 2;
}

// Not hoisted — TypeError
console.log(triple(5)); // TypeError: triple is not a function
var triple = function(n) {
    return n * 3;
};

// Arrow functions also not hoisted
console.log(quad(5)); // ReferenceError
var quad = (n) => n * 4;

Step 5: Block scoping prevents hoisting issues

// Wrong — var leaks out of block
if (true) {
    var data = 'leaked';
}
console.log(data); // leaked (pollutes outer scope)

// Right — let stays in block
if (true) {
    let data = 'blocked';
}
console.log(data); // ReferenceError: data is not defined

Prevention

• Declare all variables at the top of their scope
• Use const by default, let when reassignment is needed, never var
• Access variables only after their declaration line
• Keep function declarations at the top of the scope
• Enable ESLint no-use-before-define rule to catch hoisting bugs automatically

Common Mistakes with hoisting error

1. Non-exhaustive pattern matches that compile with warnings then crash at runtime
2. Misunderstanding that String is [Char] with poor performance for large text operations
3. Using foldl instead of foldl' causing stack overflow on large lists

These mistakes appear frequently in real-world JS code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ