import/no-named-as-default-member Suspicious

What it does

Reports the use of an exported name (named export) as a property on the default export. This occurs when trying to access a named export through the default export, which is incorrect.

Why is this bad?

Accessing a named export via the default export is incorrect and will not work as expected. Named exports should be imported directly, while default exports are accessed without properties. This mistake can lead to runtime errors or undefined behavior.

Examples

Given

// ./bar.js
export function bar() {
  return null;
}
export default () => {
  return 1;
};

Examples of incorrect code for this rule:

// ./foo.js
import foo from "./bar";
const bar = foo.bar; // Incorrect: trying to access named export via default

Examples of correct code for this rule:

// ./foo.js
import { bar } from "./bar"; // Correct: accessing named export directly

References

• Rule Source