noGlobalAssign

このコンテンツはまだ日本語訳がありません。

JavaScript (and super languages)

Summary

Rule available since: v1.5.0
Diagnostic Category: lint/suspicious/noGlobalAssign
This rule is recommended, which means is enabled by default.
This rule doesn’t have a fix.
The default severity of this rule is error.
Sources:
- Same as no-global-assign

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "suspicious": {
5
        "noGlobalAssign": "error"
6
      }
7
    }
8
  }
9
}

Description

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

Invalid

1
Object = 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.

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

1
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

1
a = 0;

1
let window;
2
window = {};