Skip to content
← Back to rules

eslint/no-global-assign Correctness

✅ This rule is turned on by default.

What it does ​

Disallow modifications to read-only global variables.

Why is this bad? ​

In almost all cases, you don't want to assign a value to these global variables as doing so could result in losing access to important functionality.

Examples ​

Examples of incorrect code for this rule:

javascript
Object = null;

Configuration ​

This rule accepts a configuration object with the following properties:

exceptions ​

type: string[]

default: []

List of global variable names to exclude from this rule. Globals listed here can be assigned to without triggering warnings.

How to use ​

To enable this rule using the config file or in the CLI, you can use:

json
{
  "rules": {
    "no-global-assign": "error"
  }
}
ts
import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "no-global-assign": "error",
  },
});
bash
oxlint --deny no-global-assign

Version ​

This rule was added in v0.0.7.

References ​