arbaeen-web-app/node_modules/eslint-plugin-import/docs/rules/no-named-default.md

import/no-named-default

Reports use of a default export as a locally named import.

Rationale: the syntax exists to import default exports expressively, let's use it.

Note that type imports, as used by Flow, are always ignored.

Rule Details

Given:

// foo.js
export default 'foo';
export const bar = 'baz';

...these would be valid:

import foo from './foo.js';
import foo, { bar } from './foo.js';

...and these would be reported:

// message: Using exported name 'bar' as identifier for default export.
import { default as foo } from './foo.js';
import { default as foo, bar } from './foo.js';