title: browserHistory.push(..) from Redux action changes URL but doesn't trigger re-render
body: <p>I'm trying to do a redirect using React Router from a Redux action creator following a <code>Fetch</code> request.</p>
  
  <p>I'm using the <code>browserHistory</code> approach to push from the action creator, like so:</p>
  
  <pre><code>import { browserHistory } from 'react-router';
  ...
  browserHistory.push('/summary');
  </code></pre>
  
  <p>This is giving me two problems:</p>
  
  <p><strong>1) History <code>basename</code> is not being prefixed.</strong></p>
  
  <p>When I configured the router history, I set a <code>basename</code> value:</p>
  
  <pre><code>useRouterHistory(createHistory)({
      basename: '/foo'
  });
  </code></pre>
  
  <p>However the <code>browserHistory.push('/summary')</code> isn't prefixing the <code>basename</code> to the URL. I was under the impression from the History docs (<a href="https://github.com/reacttraining/history#using-a-base-url" rel="nofollow noreferrer">https://github.com/reacttraining/history#using-a-base-url</a>) that it would prefix.</p>
  
  <p>As a temporary workaround for the first issue, I just hardcoded my <code>basename</code> into the <code>push</code>. Which game me my next issue.</p>
  
  <p><strong>2) The URL is updated in the browser, but the page does not re-render.</strong></p>
  
  <p>If I refresh the page after the <code>push</code> has happened, the page then renders the correct route, but it seems that the push doesn't trigger a state change to force a render.</p>
  
  <p>I did come across this <a href="https://github.com/reactjs/react-router-redux" rel="nofollow noreferrer">react-router-redux</a>, but reading the docs, it sounds like it shouldn't be necessary to do what I'm after:</p>
  
  <blockquote>
    <p>This library is not necessary for using Redux together with React
    Router. You can use the two together just fine without any additional
    libraries. It is useful if you care about recording, persisting, and
    replaying user actions, using time travel. If you don't care about
    these features, just use Redux and React Router directly.</p>
  </blockquote>
  
  <p>Can anyone see where I'm going wrong? I'm sure it's just something I'm missing rather than a bug.</p>
  
  <p>I'm currently using:</p>
  
  <ul>
  <li>Redux v3.6.0</li>
  <li>React Router v3.0.0</li>
  <li>History v3.3.0</li>
  </ul>