FrontendHaltPerformance·Intermediate·Conceptual·1 min read
Why is route-based splitting usually the first place to start?
Short interview answer
Routes are a natural, already-existing boundary that a user only needs one of at a time, so splitting there tends to remove large amounts of unused code from the initial bundle with comparatively little implementation complexity.
Key takeaway
Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.