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 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 Invalidcode-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.
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.
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.