eslint/no-void Restriction

💡 A suggestion is available for this rule.

What it does

Disallows the use of the void operator.

Why is this bad?

The void operator is often used to get undefined, but this is unnecessary because undefined can be used directly instead.

Examples

Examples of incorrect code for this rule:

void 0;
var foo = void 0;

Examples of correct code for this rule:

"var foo = bar()";
"foo.void()";
"foo.void = bar";

Configuration

This rule accepts a configuration object with the following properties:

allowAsStatement

type: boolean

default: false

If set to true, using void as a standalone statement is allowed.

How to use

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

Config (.oxlintrc.json)

{
  "rules": {
    "no-void": "error"
  }
}

CLI

oxlint --deny no-void

References

• Rule Source