<p dir="auto">Just wanted to raise something that I’ve noticed using the beta.</p>
<p dir="auto">During server-side rendering (using the custom routing and <code class="notranslate">renderToHTML</code>), there are some server-side dependencies I want to make available (for example, a means of injecting requests directly into my Hapi app so that the server-side data fetching doesn’t go through a network interface). In some cases I also have data to seed an initial Redux store based on the request.</p>
<p dir="auto">Currently I’m getting this data in by attaching custom properties to the Node <code class="notranslate">Request</code> object that’s passed in to the context.</p>
<p dir="auto">This is fine, though a little awkward. I was raising this up in case you want to make it easier to add server-specific properties to the <code class="notranslate">getInitialProps</code> context.</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">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">Should serve the pages and watch for changes</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">Going through the tutorial and setup its fine, I'm able to run <code class="notranslate">npm run dev</code> and it compiles successfully, I'm able to see "Hello Next.js" page loading, but after a few seconds the app fails.</p>
<p dir="auto">error message:</p>
<p dir="auto">`/Users/myname/Documents/hello-next/node_modules/next/dist/server/on-demand-entry-handler.js:323<br>
(0, _keys2.default)(entries).forEach(function (page) {<br>
^<br>
TypeError: lastAccessPages.includes is not a function<br>
at /Users/myname/Documents/hello-next/node_modules/next/dist/server/on-demand-entry-handler.js:336:25<br>
at Array.forEach (native)<br>
at disposeInactiveEntries (/Users/myname/Documents/hello-next/node_modules/next/dist/server/on-demand-entry-handler.js:323:32)<br>
at null._repeat (/Users/myname/Documents/hello-next/node_modules/next/dist/server/on-demand-entry-handler.js:171:5)<br>
at null.wrapper [as _onTimeout] (timers.js:275:11)<br>
at Timer.listOnTimeout (timers.js:92:15)<br>
npm ERR! code ELIFECYCLE<br>
npm ERR! errno 1<br>
npm ERR! hello-next@1.0.0 dev: next<br>
npm ERR! Exit status 1<br>
npm ERR!<br>
npm ERR! Failed at the hello-next@1.0.0 dev script.<br>
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.</p>
<p dir="auto">npm ERR! A complete log of this run can be found in:<br>
npm ERR!     /Users/myname/.npm/_logs/2017-10-19T23_08_17_041Z-debug.log`</p>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>
<ol dir="auto">
<li>Finish setup in Learnnextjs</li>
<li>run <code class="notranslate">npm run dev</code></li>
</ol>
<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>4.1.1</td>
</tr>
<tr>
<td>node</td>
<td>6.9.2</td>
</tr>
<tr>
<td>OS</td>
<td>macOs 10</td>
</tr>
<tr>
<td>browser</td>
<td>chrome</td>
</tr>
<tr>
<td>etc</td>
<td></td>
</tr>
</tbody>
</table>