Back to list

TypeScript encourages named exports over default exports, hindering SOLID design

3/10 Low

TypeScript's tooling and community practices push developers toward named exports, which contradicts SOLID principles by increasing coupling and forcing knowledge of internal identifiers. This design pressure creates poor module encapsulation and makes refactoring harder, not easier.

Category
dx
Workaround
solid
Stage
onboarding
Freshness
persistent
Scope
language
Upstream
wontfix
Recurring
Yes
Buyer Type
team
Maintainer
slow

Sources

Collection History

Query: “What are the most common pain points with TypeScript in 2025?3/27/2026

Almost every module should export only one thing... TypeScript lovers usually say is it ease refactoring but it is technically impossible. If you use default exports do you hide the identifier/name of the thing you export.

Created: 3/27/2026Updated: 3/27/2026