yes i have been wondering who uses redux without react. redux tries so hard to be a react independent library, but maybe it shouldnt. ¯\_(ツ)_/¯ the maintainers do not agree.
And why shouldn't it be independent of React? While Redux and React-Redux were developed together, the Redux core is 100% pure plain vanilla JS, and the fact that bindings exist for a whole bunch of other frameworks shows that it works fine that way.
Now, Dan and Andrew have suggested that in order to have React-Redux work properly with the upcoming async React rendering, we should possibly consider reimplementing the Redux store logic to use React component state as the basis. In other words, you'd probably do something like `import {createStore} from "react-redux"`. I'm not keen on that idea myself, and am hopeful we can find an approach that will allow use of a separate standard Redux store and still get the benefits of async React rendering down the road.
maybe what im really after is what react-router-dom does, which is reexport react-router. stop making me wire up the core library itself, if you have a binding it should "just work" (TM)
Although anecdotally the opposite (people using React without Redux) is increasing (whether they are using component state, MobX or something else), so I don’t think from that point of view (as well as others!) it would make sense for Redux to be “part of” React
