no-undefined
Added in v0.8.1Configuration
Rule Details
Disallow the use of undefined as an identifier.
The undefined variable in JavaScript is actually a property of the global object. As such, in ECMAScript 3 it was possible to overwrite the value of undefined. While ECMAScript 5 disallows overwriting undefined, it's still possible to shadow undefined, such as:
Because undefined can be overwritten or shadowed, reading undefined can give an unexpected value. (This is not the case for null, which is a keyword that always produces the same value.) To guard against this, you can avoid all uses of undefined, which is what some style guides recommend and what this rule enforces. Those style guides then also recommend:
- Variables that should be
undefinedare simply left uninitialized. (All uninitialized variables automatically get the value ofundefinedin JavaScript.) - Checking if a value is
undefinedshould be done withtypeof. - Using the
voidoperator to generate the value ofundefinedif necessary.
Examples of incorrect code for this rule:
Examples of correct code for this rule:
Options
This rule has no options.
Differences from ESLint
- A named class declaration whose name is
undefined(class undefined {}) is reported once. ESLint reports the same position twice. - An assignment-destructuring pattern with a shorthand default whose name is
undefined(e.g.({ undefined = 1 } = target)) is reported once. ESLint reports the same position twice.