The React ecosystem has a well-established culture of small components. "Split your components" is advice you will encounter in almost every guide, course, and code review. It is good advice applied to the right situations. Applied reflexively to every component over a certain size, it creates a different set of problems. Photo by StartupStockPhotos on Pixabay What Good Component Splitting Actually Achieves Before getting into when to split, it helps to be clear about what splitting should achieve. Splitting a component is worthwhile when it results in at least one of the following: Genuine reuse. The extracted component appears in multiple places in the application, or could plausibly do so. A Card component that appears on five different pages is a good candidate for extraction. A UserFormInternalHelper that only exists to break up a 300-line file is not. Reduced responsibility. The extracted component has a narrower, more clearly defined purpose than the original.…