import/no-empty-named-blocks Suspicious

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 using the config file or in the CLI, you can use:

Config (.oxlintrc.json)

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

CLI

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

References

• Rule Source