A default import binds a module’s default export to a local name chosen by the importer. That name is not the original export’s identifier, and the import does not make the whole module an object. section 13.1.1
Listing 13.5 Importing a default value along with named values
import hero, { #A
tsundere, #A
yandere, #A
} from "./4-default-export.ts"; #A
console.assert(
hero === "Ranma",
"Ranma is the hero",
);
console.assert(
tsundere === "Akane",
"Akane is the tsundere",
);
console.assert(
yandere === "Shampoo",
"Shampoo is the yandere",
);The default binding can appear alongside named imports from the same module. section 13.1.1
A default export is not special beyond its import syntax: it can also be written as `default as hero` inside a named import list. Because consumers choose its name, projects may prohibit default exports to avoid inconsistent naming. section 13.1.1
Interop can change what a default import refers to. When ESM is compiled to CommonJS, its exports are placed on an object; an ESM consumer may receive that whole object as the default import, with the intended value under its `default` property. Dual ESM and CommonJS entry points can avoid this mismatch, at the cost of build complexity and package bloat. section 13.2.1
