noRestrictedGlobals
Summary
Section titled “Summary”- Rule available since:
v1.0.0
- Diagnostic Category:
lint/style/noRestrictedGlobals
- This rule doesn’t have a fix.
- The default severity of this rule is warning.
- Sources:
- Same as
no-restricted-globals
- Same as
Description
Section titled “Description”This rule allows you to specify global variable names that you don’t want to use in your application.
References to the global identifiers error
and event
are always disallowed by this rule.
Disallowing usage of specific global variables can be useful if you want to allow a set of global variables by enabling an environment, but still want to disallow some of those.
Examples
Section titled “Examples”Invalid
Section titled “Invalid”console.log(event)
code-block.js:1:13 lint/style/noRestrictedGlobals ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠ Do not use the global variable event.
> 1 │ console.log(event)
│ ^^^^^
2 │
ℹ Use a local variable instead.
function f(event) { console.log(event)}
Options
Section titled “Options”Use the options to specify additional globals that you want to restrict in your source code.
{ "options": { "deniedGlobals": { "$": "jQuery is not allowed. Use native DOM manipulation instead.", "MooTools": "Do not use MooTools, use MeowTools instead." } }}
In the example above, the rule will emit a diagnostics if tried to use $
or MooTools
without
creating a local variable.
How to configure
Section titled “How to configure”{ "linter": { "rules": { "style": { "noRestrictedGlobals": "error" } } }}