noGlobalAssign
Diagnostic Category: lint/suspicious/noGlobalAssign
Since: v1.5.0
Sources:
- Same as:
no-global-assign
Disallow assignments to native objects and read-only global variables.
JavaScript’s environments contain numerous built-in global variables, such as window in browsers and process in Node.js.
Assigning values to these global variables can be problematic as it can override essential functionality.
Examples
Section titled ExamplesInvalid
Section titled InvalidObject = null;code-block.js:1:1 lint/suspicious/noGlobalAssign ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ A global variable should not be reassigned.
> 1 │ Object = null;
│ ^^^^^^
2 │
ℹ Assigning to a global variable can override essential functionality.
window = {};code-block.js:1:1 lint/suspicious/noGlobalAssign ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ A global variable should not be reassigned.
> 1 │ window = {};
│ ^^^^^^
2 │
ℹ Assigning to a global variable can override essential functionality.
undefined = true;code-block.js:1:1 lint/suspicious/noGlobalAssign ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ A global variable should not be reassigned.
> 1 │ undefined = true;
│ ^^^^^^^^^
2 │
ℹ Assigning to a global variable can override essential functionality.
Valid
Section titled Valida = 0;let window;window = {};