What is the temporal dead zone?

Q: What is the temporal dead zone?

**Target Audience:** Engineers preparing for JavaScript fundamentals interview questions. **Difficulty:** Easy-Medium > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text. ## 1. The Core Idea 📌 **Interview term:** the **temporal dead zone** (TDZ) is the period, in a given scope, between that scope being entered and the specific line where a let or const variable is declared. During that window, the binding already exists (JavaScript knows the name is coming) but has not been initialized, and any attempt to read or write it throws a real ReferenceError. This is genuinely different from a variable simply not existing. An undeclared name and a TDZ-bound name behave differently on the exact same operations, as verified below. ## 2. Verified: let/const Throw; var Does Not <svg class

The problem

Question presented to candidate: "What is the temporal dead zone, and how is it different from a variable simply being undefined?"

What a strong answer should cover:

The temporal dead zone (TDZ) is the span of code between entering a scope and the line where a let or const binding is actually declared, during which that binding exists but has not been initialized yet.
Accessing a variable while it is in its TDZ throws a real ReferenceError -- it is not the same as the variable being undefined.
var has no TDZ -- it is hoisted AND initialized to undefined immediately, so accessing it early just silently gives undefined instead of throwing.
Even typeof is not TDZ-safe -- typeof on a name that is declared later in the current scope with let/const throws, unlike typeof on a name that is not declared anywhere at all, which safely returns "undefined".
The TDZ is scope-local: it belongs to a specific binding in a specific scope, so an inner let of the same name as an outer variable creates its own TDZ that shadows the outer one, even before the inner declaration's line.
class declarations have a TDZ too, just like let and const -- they are not hoisted the way function declarations are.

Code / implementation expected: Yes -- a runnable snippet showing let/const throwing ReferenceError before their declaration line, contrasted with var's hoisted-undefined behavior.

temporal-dead-zone

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for JavaScript fundamentals interview questions. Difficulty: Easy-Medium

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text.

1. The Core Idea

📌 Interview term: the temporal dead zone (TDZ) is the period, in a given scope, between that scope being entered and the specific line where a let or const variable is declared. During that window, the binding already exists (JavaScript knows the name is coming) but has not been initialized, and any attempt to read or write it throws a real ReferenceError.

This is genuinely different from a variable simply not existing. An undeclared name and a TDZ-bound name behave differently on the exact same op

The solution is hidden so you can try first

7 min read · 8 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

JavaScriptlet/const throw in the TDZ; var silently returns undefined (run directly)