Maybe? It depends on your teams' requirements and how the project will be developed over time. For instance, if many small, rapidly-changing components will be added over time this kind of organization might be beneficial to keep git logs simple and readable. On the other hand, if you have fewer but larger components that, say, heavily depend on each other and/or mandate heavy use of async data fetching or side-effects (redux-saga) then this approach might lend itself to fragmentation and many implicit inter-dependencies that would be difficult to track down.
I'll have to think about this more...