import/no-empty-named-blocks Suspicious

🛠️ An auto-fix is available for this rule.

What it does

Enforces that named import blocks are not empty.

Why is this bad?

Empty named imports serve no practical purpose and often result from accidental deletions or tool-generated code.

Examples

Examples of incorrect code for this rule:

import {} from "mod";
import Default from "mod";

Examples of correct code for this rule:

import { mod } from "mod";
import Default, { mod } from "mod";

How to use

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

CLI

oxlint --deny import/no-empty-named-blocks --import-plugin

Config (.oxlintrc.json)

{
  "plugins": ["import"],
  "rules": {
    "import/no-empty-named-blocks": "error"
  }
}

References

• Rule Source