<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/zeit/next.js/issues?q=is%3Aissue">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Context</h2>
<p dir="auto">Kept getting a <code class="notranslate">store.runSagaTask is not a function</code> error after copying the <a class="issue-link js-issue-link notranslate" rel="noopener noreferrer nofollow" href="https://linear.app/vercel/issue/NEXT-redux-saga">next-redux-saga</a> example. Then I discovered the <a href="https://github.com/bmealhouse/next-redux-saga">next-redux-saga</a> repo has <a href="https://github.com/bmealhouse/next-redux-saga#configure-store">different code for <code class="notranslate">store.js</code></a>:</p>
<div class="highlight highlight-source-diff notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="-  store.sagaTask = sagaMiddleware.run(rootSaga)
+  store.runSagaTask = () =&gt; {
+    store.sagaTask = sagaMiddleware.run(rootSaga)
+  }
+
+  // run the rootSaga initially
+  store.runSagaTask()"><pre class="notranslate"><span class="pl-md"><span class="pl-md">-</span>  store.sagaTask = sagaMiddleware.run(rootSaga)</span>
<span class="pl-mi1"><span class="pl-mi1">+</span>  store.runSagaTask = () =&gt; {</span>
<span class="pl-mi1"><span class="pl-mi1">+</span>    store.sagaTask = sagaMiddleware.run(rootSaga)</span>
<span class="pl-mi1"><span class="pl-mi1">+</span>  }</span>
<span class="pl-mi1"><span class="pl-mi1">+</span></span>
<span class="pl-mi1"><span class="pl-mi1">+</span>  // run the rootSaga initially</span>
<span class="pl-mi1"><span class="pl-mi1">+</span>  store.runSagaTask()</span></pre></div>
<p dir="auto">Would it be all right if I opened a PR with that change?</p>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/zeit/next.js/issues?q=is%3Aissue">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>


<p dir="auto">Navigating to another <em>non-built</em> page should navigate after page has built successfully.</p>
<h2 dir="auto">Current Behavior</h2>


<p dir="auto">Navigating to another <em>non-built</em> page reloads the page after intended page has built successfully. Clicking to navigate again after the intended page has been built, correctly routes to the page.</p>


<h2 dir="auto">Context</h2>


<p dir="auto">Just more of a pain in development because we aren't sure that it isn't happening in a production build without double checking every time.</p>
<p dir="auto">I am running a custom express server with custom document and app.</p>
<h2 dir="auto">Your Environment</h2>

<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>next</td>
<td>v6</td>
</tr>
<tr>
<td>node</td>
<td>v9.11.1</td>
</tr>
<tr>
<td>OS</td>
<td>Windows 10</td>
</tr>
<tr>
<td>browser</td>
<td>Chrome 66</td>
</tr>
<tr>
<td>etc</td>
<td></td>
</tr>
</tbody>
</table>