Good post overall. I do have a couple bits of feedback.
First, the React community has always been much more of a “DIY/pick-and-choose” mindset, because of React’s “just the V” behavior as opposed to the all-in-one approach of Angular or Ember. So, it’s natural that that would extend to component libs as well.
Second, some good places to look for React component libs are https://js.coach and https://github.com/brillout/awesome-react-components . I also have links to other useful React resource collections in the Community Resources section of my React/Redux links list.
Third, you work for or are associated with Telerik, right? I would venture a guess that your background and experience there are coloring your perspectives on the state of React UI libs, especially in terms of “comprehensive UI suites” and “complex components like grids and charts”. The .NET ecosystem (and really much of Microsoft’s developer ecosystem over the years) has historically been heavily used by enterprise applications and line-of-business apps, with desires for complex functionality out of the box. That has enabled companies like Telerik to build and offer large widget packages like Kendo UI for sale.
However, there’s also a lot of activity outside the enterprise LOB app world, and that’s where React has picked up a lot of its adoption thus far. So, it’s not surprising that there hasn’t been as much emphasis on integrated component libraries or full-blown, do-it-all grids. (That said, there _are_ quite a few grids out there — see those lists.)
Hopefully that adds just a bit of context to the discussion.