you can enact most of the behavior of redux with a simple component

state-component.js

/* this lacks subscribe behavior or ability to dispatch from outside of component tree but that is generally not neccesary */
class State extends React.Component {
  constructor(props) {
    super(props); 
    this.state = YOUR_INITIAL_STATE;
  }
  reducer = (action, state, props) => {...newState};
  /* setState takes an object of new state as first arg or a function of props and state that returns new state 
   * which we will use here
   * we pass dispatch around and use it similarly to redux dispatch
  */
  dispatch = action => this.setState(reducer.bind(null, action));
  render() {
    return <App {...this.state} {...this.props} dispatch={this.dispatch} />;
  }
}

state-hoc.js

/* we can also use a HOC to maintain state for a specific subtree */
function stateHOC(Component, initState, reducer) {
  return class State extends React.Component {
    constructor(props) {
      super(props);
      this.state = initState;
    }
    dispatch = action => this.setState(reducer.bind(this, action));
    render() {
      return <Component {...this.state} {...this.props} dispatch={this.dispatch} />;
    }
  }
}

Can you add some examples on how to use it?

where the newState comes from? also for return {} I think it needs to ({})

https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367

@tiansijie it's just pseudocode representing the fact that function will return a new state object