FrontendHaltPerformance·Intermediate·Coding·1 min read
How can a bundle analyzer catch a code-splitting mistake that seems to work correctly?
Short interview answer
It's possible for an application-wide import elsewhere to pull an intended-to-be-lazy dependency back into the main chunk without any error; a bundle analyzer visualizes what's actually in each chunk, revealing that the split didn't achieve its intended savings.
Key takeaway
Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.