import/no-named-as-default

Reports use of an exported name as the locally imported name of a default export.

Rationale: using an exported name as the name of the default export is likely...

Rule Details

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

...this would be valid: js import foo from './foo.js';

...and this would be reported: js // message: Using exported name 'bar' as identifier for default export. import bar from './foo.js';

For post-ES2015 export extensions, this also prevents exporting the default from a referenced module as a name within that module, for the same reasons:

```js // valid: export foo from './foo.js'

// message: Using exported name 'bar' as identifier for default export. export bar from './foo.js'; ```

Further Reading