<p dir="auto">HTML elements at  <a href="https://github.com/zeit/next.js/search?utf8=%E2%9C%93&amp;q=%3CHead%3E&amp;type=">in many in examples are using single quote</a> instead of double but examples in readme and blog of zeit are not. IMO It might make users confused specially in terms of using lint like standard, which report an error of double quotes in JSX. I'm not sure which style is your recommendation.</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">Using consistence expression for quote</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">Using mixin styles between examples project and document</p>
<p dir="auto">I'm trying <code class="notranslate">next export</code> in an app that uses apollo client to load content from our CMS. When navigating from page to page via  or imperative Router actions w/ prefetching, <code class="notranslate">getInitialProps</code> fires on page load &amp; emits a call to my graphql API.</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">I'd hoped that the static export process would 'pre-hydrate' the apollo cache such that the data for a route is packed into the HTML/JS of the route payload. When loading a route, then, no calls should be fired to the content API at all (we don't have any dynamic content).</p>
<p dir="auto">This works fine when fetching the response w/ <code class="notranslate">curl</code> or something, and when navigating directly to a route, no calls are fired to our API endpoint (per the Network tab).</p>
<p dir="auto">My expectation is that no API calls would be fired when loading subsequent routes accessed via <code class="notranslate">&lt;Link prefetch&gt;</code></p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">When clicking a prefetch link (or using the imperative <code class="notranslate">Router.prefetch</code>), <code class="notranslate">getInitialProps</code> is fired on route transition &amp; I get a 'loading' state.</p>
<p dir="auto">If I use vanilla <code class="notranslate">&lt;a&gt;</code>, the transition happens as expected and no API call is fired. But, there's no prefetching w/ this option, so not really ideal.</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>4.14</td>
</tr>
<tr>
<td>node</td>
<td>8.6</td>
</tr>
<tr>
<td>OS</td>
<td>win10 w/ WSL    bash</td>
</tr>
<tr>
<td>browser</td>
<td>chrome 62</td>
</tr>
<tr>
<td>etc</td>
<td></td>
</tr>
</tbody>
</table>