You'll get the following values in the alerts: true, "undefined", "undefined", true, false, "undefined", "object", true.

For some strange reason, JavaScript enables you to redefine "undefined". Just in case you're wondering, undefined is not just some variable that happens to be undefined, it is an official primitive value (but not a keyword). If you declare a variable but don't set its value, it gets that undefined value. Now after our silly redefinition of the undefined, typeof(a) is "undefined" but typeof(undefined) is "object", which more or less means that undefined is not undefined. Nice.

So why would anyone in their right minds define undefined? I don't have the beginning of a clue, but that means that strict comparison to undefined is broken (as the code above demonstrates) and that typeof(a) === 'undefined' should be used instead (at least in principle).

This is so much fun! So any other important primitive values we can overwrite just to see what happens? Sure, let's try this:

Curiously enough, JavaScript seems to let you define NaN without throwing, but it actually doesn't do it: the alerts here show true, NaN and true.

From what I can tell, this redefinition of a primitive value seems to be "valid" only for undefined. Null can't be assigned to, neither can true, false or numbers. Too bad, how fun would that have been (in true daily WTF style):