<p dir="auto">In the React context, when building an app I'm used to the concept of containers and components. It appears to me that "pages" are somewhat equivalent to containers within next.js.</p>
<p dir="auto">Is there a recommended way to add an application layout container such that I could specify for example global <code class="notranslate">&lt;Header/&gt;</code> and <code class="notranslate">&lt;Footer/&gt;</code> components with the router determining which content to display within (the page)? Similar to how the popular <code class="notranslate">react-router</code> package <code class="notranslate">match</code> function can be configured on the server.</p>
<p dir="auto">Using the next.js default router and pages folder as is, to achieve this do I have no option but to duplicate <code class="notranslate">&lt;Header/&gt;</code> and <code class="notranslate">&lt;Footer/&gt;</code> across all pages?</p>
<p dir="auto">Hi,</p>
<p dir="auto">I've been seeing deployment errors with my Next.js project using Now. My project runs as expected on my own device and when I try to deploy I get several build errors, I suspect it has something to do with my build scripts. The project with previous deployments had worked just fine before, I recently added dynamic importing of some components. Maybe this has something to do with how the Now servers are building the deployment. Thanks for taking a look!</p>


<ul dir="auto">
<li>[x ] 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">Just trying to deploy to now.</p>

<h2 dir="auto">Current Behavior</h2>

<p dir="auto">`</p>
<blockquote>
<p dir="auto">sh: next: not found<br>
npm ERR! file sh<br>
npm ERR! code ELIFECYCLE<br>
npm ERR! errno ENOENT<br>
npm ERR! syscall spawn<br>
npm ERR! jm-site-react@1.0.0 build: <code class="notranslate">next build</code><br>
npm ERR! spawn ENOENT<br>
npm ERR!<br>
npm ERR! Failed at the jm-site-react@1.0.0 build script.<br>
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.<br>
npm ERR! A complete log of this run can be found in:<br>
npm ERR!     /home/nowuser/.npm/_logs/2017-08-17T19_26_59_314Z-debug.log<br>
`</p>
</blockquote>

<h2 dir="auto">Steps to Reproduce (for bugs)</h2>


<ol dir="auto">
<li>download this repo: <a href="https://github.com/jay-manday/jm-site-react/tree/responsive-p5">https://github.com/jay-manday/jm-site-react/tree/responsive-p5</a></li>
<li><code class="notranslate">git checkout responsive-p5</code></li>
<li>yarn</li>
<li>now deploy</li>
</ol>
<h2 dir="auto">Context</h2>


<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>latest</td>
</tr>
<tr>
<td>node</td>
<td>8.0.0</td>
</tr>
<tr>
<td>OS</td>
<td>Mac OSX 10.12.5</td>
</tr>
<tr>
<td>browser</td>
<td>Chrome</td>
</tr>
<tr>
<td>etc</td>
<td></td>
</tr>
</tbody>
</table>