undefined, null, and naming every type

Most languages have one way of saying there is nothing here. JavaScript has two, and the difference between them is a difference of authorship: undefined is what the language leaves behind when nobody supplied a value, and null is what a programmer writes down when they mean deliberately empty.

The distinction is not academic. An address field holding undefined says nobody has filled this in yet. The same field holding null says a person considered it and recorded that there is no address. One is a gap in the process; the other is a fact about the world.

You will rarely type undefined. It arrives by itself, in exactly the situations where a value was expected and none was ever provided: a let declared with no value yet, a property asked for on an object that does not have it, a function that finished without handing anything back — including console.log, which is why the earlier lesson said it gives you nothing you can use.

That is why undefined so often shows up as the first symptom of a bug elsewhere. It is rarely wrong in itself; it is a message that something upstream never happened. When you see it, the useful question is not what is undefined but which step was supposed to fill this in.

null never appears by accident. It is in your program because somebody wrote it, which makes it a record of intent: we looked, and there is nothing, and that is the final answer.

Use it when absence is a real, meaningful state — no middle name, no discount applied, no manager for this employee. Reach for it sparingly. A value that is sometimes a number and sometimes null forces every piece of code downstream to cope with both, and the module on errors and robustness looks hard at when that cost is worth paying.

typeof is an operator, not a function — it goes in front of a value with a space, and the brackets you often see around its operand are just ordinary grouping brackets. What it hands back is a piece of TEXT naming the kind of value: the six characters n-u-m-b-e-r, not the number type itself. So typeof 42 === "number" is a comparison of two strings, and it is true.

Here is the full set of kinds JavaScript has. Seven of them are PRIMITIVE — simple, single values that cannot be taken apart: undefined, null, boolean, number, string, plus bigint for very large whole numbers and symbol for unique keys. Everything else is an OBJECT: arrays, dates, the collections in module 4, and functions, which are objects you can call.

typeof reports those honestly with two footnotes. Functions get their own answer, "function", even though a function is an object. And null reports as "object", which is simply wrong — it is a bug from the first version of JavaScript in 1995 that cannot be fixed now without breaking a large fraction of the web. Everybody who writes JavaScript knows this one; you now do too.

Testing for null with typeof. Because typeof null is "object", a check written as typeof value === "object" is true for null, and code that then reaches inside the value stops with an error. Compare with value === null instead; it is exact and it is short.

Quoting them. The text "undefined" and the value undefined are as different as the text "7" and the number 7. A check against the quoted version passes only for a value that is genuinely a piece of text spelling out the word, which is almost never what you meant.

Assuming a name exists. Asking for a name that was never declared normally stops the program — but typeof is the one operator allowed to ask about a name that does not exist, and it answers "undefined" rather than failing. That is occasionally useful and frequently confusing, because it means a typo in a name can look like an absent value rather than a mistake.

Look at the errors real applications report and a large share are one sentence: something was expected and nothing was there. Not a wrong calculation — an absence, arriving somewhere that assumed a presence.

Everything later in this course that deals with that problem — optional chaining, default values, validating at the boundary, returning an outcome instead of throwing — is built on the distinction you have just learned. Knowing which nothing you have, and whether it means not yet or none, is what makes those tools make sense rather than seeming like syntax to memorise.

undefined is the language's placeholder when no value was ever supplied; null is a programmer's deliberate mark of emptiness. typeof produces a piece of text naming a kind of value. There are seven primitive kinds — undefined, null, boolean, number, string, bigint, symbol — and everything else is an object. typeof null says "object", which is a preserved 1995 bug; test with === null instead.