The differences between null and undefined
null and undefined share abstract equality == but not strict equality ===,
They represent slightly different things:
undefined represents the absence of a value, such as before an identifier/Object property has been created or in the period between identifier/Function parameter creation and it's first set, if anynull represents the intentional absence of a value for an identifier or property which has already been created
They are different types of syntax:undefined is a property of the global Object, usually immutable in the global scope. This means anywhere you can define an identifier other than in the global namespace could hide undefined from that scope (although
things can still be undefined) null is a word literal, so it's meaning can never be changed and attempting to do so will throw an Error.
The similarities between null and undefined
null and undefined are both falsy
Neither null or undefined equal false
Using undefinedIf the current scope can't be trusted, use something which evaluates to undefined, for example void 0;.If undefined is shadowed by another value, it's just as bad as shadowing Array or Number.Avoid setting something as undefined. If you want to remove a property bar from an Object foo, delete foo.bar; instead.Existence testing identifier foo against undefined could throw a Reference Error, use typeof foo against "undefined" instead.