src/content/docs/linter/rules/no-global-assign.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> ## Summary - Rule available since: `v1.5.0` - Diagnostic Category: [`lint/suspicious/noGlobalAssign`](/reference/diagnostics#diagnostic-category) - This rule is **recommended**, meaning it is enabled by default. - This rule doesn't have a fix. - The default severity of this rule is [**error**](/reference/diagnostics#error). - Sources: - Same as [`no-global-assign`](https://eslint.org/docs/latest/rules/no-global-assign){
"linter": {
"rules": {
"suspicious": {
"noGlobalAssign": "error"
}
}
}
}
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.
Object = null;
window = {};
undefined = true;
a = 0;
let window;
window = {};