import/no-named-as-default
Disallow naming a default import after a named export of the same module
Also called import-x/no-named-as-default
import Button from "./button" gets the default export, whatever you call it. If ./button also has a named export Button, you probably forgot the braces, and the code is using a different value than the name suggests.
The rule reads the imported module. It only reports if that module has both a default export and a named export with the name you chose.
Configure#
Off by default. To turn it on:
bunfig.toml
[lint.rules]
"import/no-named-as-default" = "error" # or "warn"Examples#
Reported:
button.js
export const Button = props => render("button", props);
export default withTheme(Button);example.js1 problem
import ButtonUsing exported name Button as identifier for default import. from "./button";Not reported:
button.js
export const Button = props => render("button", props);
export default withTheme(Button);example.jsNo problems
import ThemedButton, { Button } from "./button";When not to use it#
Some modules export the same value both ways on purpose, so that import Button and import { Button } both work. The rule still reports the first form there.