# When React compound components are a poor fit for data-driven lists

DevFeed: [When React compound components are a poor fit for data-driven lists](<https://devfeed.tech/articles/you-re-using-react-compound-components-wrong-18121.md>)

Original publisher: [Read original article](<https://thetshaped.dev/p/you-are-using-react-compound-components-wrong-type-safe-typescript>)

Author: The T-Shaped Dev

Published: 2026-06-16T10:19:04Z

Content type: tutorial

Language: en

Sources: [The T-Shaped Dev](<https://devfeed.tech/sources/the-t-shaped-dev.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>)

Tags: [components](<https://devfeed.tech/tags/components.md>), [react](<https://devfeed.tech/tags/react.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

## AI overview

The article argues that React compound components are often misapplied to data-driven lists. It explains that when items come from an array, a plain props-based API better supports operations such as sorting, filtering, virtualization, and keyboard navigation, while avoiding unnecessary TypeScript complexity.

## Source excerpt

The most-copied example in every tutorial is the one place you shouldn't use them.