What are the quirks of the typeof operator?

Q: What are the quirks of the typeof operator?

**Target Audience:** Engineers preparing for JavaScript fundamentals interviews. **Difficulty:** Easy > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Every result below, including the real thrown error, was actually run in Node. ## 1. Why This Even Matters — A Story First Asking "does this specific book exist anywhere in the library?" is a genuinely safe question to ask even if the book's title was never catalogued at all — you get a plain "no" back, no drama. Directly demanding "hand me that specific book right now," by contrast, genuinely fails loudly if the book was never catalogued — there is nothing to hand over. `typeof` is the safe "does it exist" question; a bare variable reference is the direct demand. ## 2. The Core Idea 📌 **Interview term:** `typeof` on a genuinely undeclared variable safely returns `"undefined"`, with no throw — a real, deliberate exception to the normal rule that referencin

The problem

Question presented to candidate: "If a variable was genuinely never declared anywhere, does typeof someUndeclaredVar throw an error? What if you just wrote someUndeclaredVar directly, without typeof — same answer?"

What a strong answer should cover:

📌 Interview term: the real, direct answer to the prompt — verified directly: typeof on a genuinely undeclared variable does NOT throw at all — it genuinely returns the string "undefined". A bare reference to that SAME undeclared variable, without typeof, genuinely DOES throw a real ReferenceError — typeof is a real, deliberate special case, safely checking for a variable's existence without risking a crash.
📌 Interview term: typeof null is "object" — a famous, real historical bug, preserved for backward compatibility — covered in more depth in this bank's own dedicated null-vs-undefined question.
📌 Interview term: typeof on arrays and NaN — verified directly: typeof [] is genuinely "object", not a separate "array" category (Array.isArray() is the correct, dedicated check); typeof NaN is genuinely "number", since NaN is a real, valid (if invalid-representing) member of the Number type.
📌 Interview term: functions are the one real exception — verified directly: typeof on a function (including a class, which is genuinely a function under the hood) returns "function" — the ONE value typeof can return that does not correspond to one of the七 formal ECMAScript language types directly, a real, deliberate special case for a callable value.
A precise answer names typeof genuinely returning a real result for every one of the primitive types plus "object"/"function"/"undefined" — Symbol() genuinely returns "symbol", and a BigInt literal genuinely returns "bigint" — verified directly, confirming typeof stays accurate for every newer primitive type added to the language too.

Clarifying questions expected:

None — this is a definitional/technical question; directly answering the prompt's own undeclared-variable scenario (typeof vs. bare reference) is the strong signal, since it is the single most useful, commonly-missed typeof quirk.

Code / implementation expected: Yes — the direct side-by-side typeof undeclaredVar vs. a bare undeclaredVar reference is the clearest, most convincing demonstration.

typeof

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 interviews. Difficulty: Easy

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Every result below, including the real thrown error, was actually run in Node.

1. Why This Even Matters — A Story First

Asking "does this specific book exist anywhere in the library?" is a genuinely safe question to ask even if the book's title was never catalogued at all — you get a plain "no" back, no drama. Directly demanding "hand me that specific book right now," by contrast, genuinely fails loudly if the book was never catalogued — there is nothing to hand over. typeof is the safe "does it exist" question; a bare variable reference is the direct demand.

2. The Core Idea

📌 Interview term: typeof on a genuinely undeclared variable safely returns `"undef

The solution is hidden so you can try first

5 min read · 8 sections

Run the code

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

JavaScriptReal proof: typeof on an undeclared variable genuinely never throws, while a bare reference to it genuinely does