Revisit default exports

[Lemmingh]

Proposal

Convert default exports to named exports.

Avoid default exports in future.

Background

There was a time when I thought default exports are succinct. However, they introduce insidious problems. It will be dangerous to mix named and default exports in our codebase after #1077.

• Interoperability. Module systems apply different constraints and semantics. For example, CommonJS exports and module.exports are incompatible with ECMAScript export default. A real-world case is our hard time with highlight.js.

• Maintainability. Default exports make it much harder to find references, due to implicit name conversion and inconsistent import pattern. See Google's rationale.

[yzhang-gh]

Haven't ever paid much attention to this. It looks like currently most of the existing exports are named exports, right?
I am of course okay with it.

[Lemmingh]

currently most of the existing exports are named exports

Yes.

The few default exports were introduced by me. 😂

---

For reference, the lesson from Highlight.js:

• 8df58cd
• (chore) export named HighlightJS export in Node packages highlightjs/highlight.js#3307