eslint/no-empty-static-block Correctness

✅ This rule is turned on by default.

💡 A suggestion is available for this rule.

What it does

Disallows the usages of empty static blocks

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.

Example

Examples of incorrect code for this rule:

class Foo {
  static {}
}

Examples of correct code for this rule:

class Foo {
  static {
    // blocks with comments are allowed
  }
}
class Bar {
  static {
    doSomething();
  }
}

How to use

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

CLI

oxlint --deny no-empty-static-block

Config (.oxlintrc.json)

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

References

• Rule Source