Pattern: Named default import
Issue: -
Using named import syntax for default exports (import { default as foo }
) is unnecessarily verbose when a simpler default import syntax (import foo
) exists for this purpose.
Example of incorrect code:
import { default as foo } from "./foo.js";
import { default as foo, bar } from "./foo.js";
Example of correct code:
import foo from "./foo.js";
import foo, { bar } from "./foo.js";