I've been down this road a few times. See my question here, which Dan Abramov himself chimed in on: reddit.com/r/reactjs/comments/6al7h2/facebook_has…

Short answer is: it depends. But for medium to larger type apps, your structure above will become implicit very fast, meaning its too abstract to give declarative meaning into the functionality of your app. Looking at the directories will be hard to track down the code you (or a new developer) are looking for.

I prefer to break things out by features or pages. No matter how react-y you are, your app will likely have pages, so its fair to piggy back off of that in terms of structure.

This is how I like it:

/src
_/components  <-- shared/global components
_/pages
___/PAGE_NAME
____/containers
____/components    <--  components highly specific to that page
____/index.js