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";

Options

allowAsStatement

{ type: boolean, default: false }

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

How to use

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

CLI

oxlint --deny no-void

Config (.oxlintrc.json)

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

References

• Rule Source