<p dir="auto">Now that Prettier supports config files it would be much simpler to support a style for the <code class="notranslate">examples/</code> directory. I know you use Standard as per <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="217414059" data-permission-text="Title is private" data-url="https://github.com/vercel/next.js/issues/1527" data-hovercard-type="issue" data-hovercard-url="/vercel/next.js/issues/1527/hovercard" href="https://github.com/vercel/next.js/issues/1527">#1527</a>, I'm only suggesting this for the <code class="notranslate">examples/</code> directory. A lot of the React, JS and TS community are moving to Prettier and are also the people to create the examples in this repo. By having a <code class="notranslate">.prettierrc</code> in the <code class="notranslate">examples/</code> directory everyone who uses Prettier would not need to turn off or alter their settings each time they want to contribute (I've been struggling with this all day on various repos).</p>
<p dir="auto">Again, this is not a suggestion to run Prettier over the Next.js source, just a config in the <code class="notranslate">examples/</code> directory.</p>
<p dir="auto">I don't intend to start a long discussion on this, I just thought the friction might be much lower now Prettier has configs. Feel free to close this without discussion if it is not of interest to any maintainers.</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>
<p dir="auto">This config seems to apply a style almost identical to the current styling of some of the examples from Next.js Maintainers.</p>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;tabWidth&quot;: 2,
  &quot;trailingComma&quot;: &quot;none&quot;,
  &quot;printWidth&quot;: 100,
  &quot;singleQuote&quot;: true,
  &quot;semi&quot;: false
}
"><pre class="notranslate">{
  <span class="pl-ent">"tabWidth"</span>: <span class="pl-c1">2</span>,
  <span class="pl-ent">"trailingComma"</span>: <span class="pl-s"><span class="pl-pds">"</span>none<span class="pl-pds">"</span></span>,
  <span class="pl-ent">"printWidth"</span>: <span class="pl-c1">100</span>,
  <span class="pl-ent">"singleQuote"</span>: <span class="pl-c1">true</span>,
  <span class="pl-ent">"semi"</span>: <span class="pl-c1">false</span>
}
</pre></div>
<p dir="auto">PS: thanks for your work!</p>
<p dir="auto">In the <code class="notranslate">next/babel.js</code> the babel-runtime module is aliased to use a local version. This is bad practise, since the build script should use any available version of <code class="notranslate">babel-runtime</code>, which allows me to use my own.</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">In <code class="notranslate">dist/server/build/babel/preset.js</code> on line <code class="notranslate">:24</code> there is an alias for <code class="notranslate">babel-runtime</code> to relatively resolve it inside of next.js. This should be removed, so any version of <code class="notranslate">babel-runtime</code> inside the <code class="notranslate">node_modules</code> folder is used, not just the one in <code class="notranslate">next/node_modules</code></p>

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


<p dir="auto">The build script throws an error, since all <code class="notranslate">babel-runtime</code> modules are <code class="notranslate">undefined</code>.<br>
Currently generated when building:<br>
<code class="notranslate">var _regenerator = require('next/node_modules/babel-runtime/regenerator');</code><br>
Expected/wanted behaviour when building:<br>
<code class="notranslate">var _regenerator = require('babel-runtime/regenerator');</code></p>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>


<ol dir="auto">
<li>Have a module (let's call it <code class="notranslate">module-a</code>) with <code class="notranslate">next</code> as <code class="notranslate">devDependecy</code></li>
<li>In <code class="notranslate">modula-a</code>, use <code class="notranslate">next/babel</code> as babelrc preset</li>
<li>Build <code class="notranslate">module-a</code> to a lib folder</li>
<li>In the generated lib files, <code class="notranslate">var _regenerator = require('next/node_modules/babel-runtime/regenerator');</code> is now inserted at the top</li>
<li>Use <code class="notranslate">module-a</code> in another project (<code class="notranslate">module-b</code>) that doesn't have <code class="notranslate">next</code> as <code class="notranslate">dependency</code>.</li>
<li>Build <code class="notranslate">module-b</code></li>
<li>The build script throws an error, since all <code class="notranslate">babel-runtime</code> modules are <code class="notranslate">undefined</code> (<code class="notranslate">next</code> is not installed in <code class="notranslate">module-b</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>3.0.6</td>
</tr>
</tbody>
</table>