<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">next@latest should add without incorrect peer dependency</p>
<h2 dir="auto">Current Behavior</h2>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="&gt;yarn add react@latest react-dom@latest next@latest
yarn add v1.2.0
info No lockfile found.
[1/4] Resolving packages...
warning next &gt; glob-promise &gt; semantic-release &gt; npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
warning next &gt; glob-promise &gt; semantic-release &gt; @semantic-release/condition-travis &gt; travis-deploy-once &gt; travis-ci &gt; request &gt; node-uuid@1.4.8: Use uuid module instead
[2/4] Fetching packages...
info fsevents@1.1.2: The platform &quot;win32&quot; is incompatible with this module.
info &quot;fsevents@1.1.2&quot; is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning &quot;styled-jsx@2.0.2&quot; has incorrect peer dependency &quot;react@15.x.x&quot;.
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 618 new dependencies."><pre class="notranslate"><code class="notranslate">&gt;yarn add react@latest react-dom@latest next@latest
yarn add v1.2.0
info No lockfile found.
[1/4] Resolving packages...
warning next &gt; glob-promise &gt; semantic-release &gt; npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
warning next &gt; glob-promise &gt; semantic-release &gt; @semantic-release/condition-travis &gt; travis-deploy-once &gt; travis-ci &gt; request &gt; node-uuid@1.4.8: Use uuid module instead
[2/4] Fetching packages...
info fsevents@1.1.2: The platform "win32" is incompatible with this module.
info "fsevents@1.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "styled-jsx@2.0.2" has incorrect peer dependency "react@15.x.x".
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 618 new dependencies.
</code></pre></div>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="&gt;yarn check
yarn check v1.2.0
error &quot;next#styled-jsx#react@15.x.x&quot; doesn't satisfy found match of &quot;react@16.0.0&quot;
error Found 1 errors.
info Visit https://yarnpkg.com/en/docs/cli/check for documentation about this command."><pre class="notranslate"><code class="notranslate">&gt;yarn check
yarn check v1.2.0
error "next#styled-jsx#react@15.x.x" doesn't satisfy found match of "react@16.0.0"
error Found 1 errors.
info Visit https://yarnpkg.com/en/docs/cli/check for documentation about this command.
</code></pre></div>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>


<ol dir="auto">
<li>
<p dir="auto">yarn add react@latest react-dom@latest next@latest on Windows 7 laptop</p>
</li>
<li>
<p dir="auto">Also try</p>
</li>
</ol>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="&gt;yarn check"><pre class="notranslate"><code class="notranslate">&gt;yarn check
</code></pre></div>
<p dir="auto">After adding.</p>
<h2 dir="auto">Context</h2>
<p dir="auto">I am currently developing an app with Next@3 and using React@15/Styled-JSX. I am now trying to install Next@4 and thought of using React@16/Styled-JSX@2. Not sure if this is an error with Yarn.<br>
Apologize if this is a duplicate issue or a silly one.</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.0.3</td>
</tr>
<tr>
<td>node</td>
<td>8.1.2</td>
</tr>
<tr>
<td>OS</td>
<td>Windows 7</td>
</tr>
<tr>
<td>browser</td>
<td>N/A</td>
</tr>
<tr>
<td>etc</td>
<td>N/A</td>
</tr>
</tbody>
</table>
<p dir="auto">When doing a static export with assetPrefix defined in next.config.js, stylesheet does not link properly.</p>
<p dir="auto">Script files are included as <code class="notranslate">&lt;assetPrefix&gt;/_next/&lt;...&gt;/index.js</code>, while the css file is included as <code class="notranslate">/_next/static/style.css</code> with no prefix.</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">Current Behavior</h2>
<p dir="auto">Stylesheet is linked as <code class="notranslate">/_next/static/style.css</code> with no prefix when assetPrefix is defined</p>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">Stylesheet should be linked as <code class="notranslate">&lt;assetPrefix&gt;/_next/static/style.css</code> when assetPrefix is defined</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>canary (07-03-2018)</td>
</tr>
<tr>
<td>node</td>
<td>v8.4.0</td>
</tr>
<tr>
<td>OS</td>
<td>macOS Sierra</td>
</tr>
<tr>
<td>browser</td>
<td>Chrome Version 63.0.3239.132</td>
</tr>
</tbody>
</table>