eslint/no-empty Restriction

💡 A suggestion is available for this rule.

What it does

Disallows empty block statements

Why is this bad?

Empty block statements, while not technically errors, usually occur due to refactoring that wasn’t completed. They can cause confusion when reading code.

Examples

Examples of incorrect code for this rule:

if (condition) {
}

Examples of correct code for this rule:

if (condition) {
  throw new Error("condition should be false");
}

Configuration

This rule accepts a configuration object with the following properties:

allowEmptyCatch

type: boolean

default: false

If set to true, allows an empty catch block without triggering the linter.

How to use

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

CLI

oxlint --deny no-empty

Config (.oxlintrc.json)

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

References

• Rule Source