<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">Hi there,</p>
<p dir="auto">I want to setup this node_module <a href="https://react-styleguidist.js.org/docs/webpack#create-react-app-typescript" rel="nofollow">https://react-styleguidist.js.org/docs/webpack#create-react-app-typescript</a></p>
<p dir="auto">and in order for it to work, it needs to access the webpack.config, how do I go about exposing that to this node_module?</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>
<p dir="auto">I built my Next app and deployed it as I usually do, but when loading the page, I got the following on the browser:</p>
<p dir="auto"><code class="notranslate">Uncaught ReferenceError: webpackJsonp is not defined</code> in main.js 1:1</p>
<p dir="auto">Also, all JS interactivity was broken, but the style/design of the website was looking okay.</p>
<p dir="auto">Here is the beginning of main.js file:</p>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="module.exports =
webpackJsonp([0],{"><pre class="notranslate"><span class="pl-smi">module</span><span class="pl-kos">.</span><span class="pl-c1">exports</span> <span class="pl-c1">=</span>
<span class="pl-s1">webpackJsonp</span><span class="pl-kos">(</span><span class="pl-kos">[</span><span class="pl-c1">0</span><span class="pl-kos">]</span><span class="pl-kos">,</span><span class="pl-kos">{</span></pre></div>
<p dir="auto">I rebuilt and redeployed the application and it disappeared.</p>
<p dir="auto">I believe it is because I had a running Next.js app while building, and I was changing the code on it, which trigger other rebuilds. It probably messed up the build process (the first main.js wasn't uglified at all, while the new/fixed version I have now is correctly uglified/onelined)</p>
<p dir="auto">I'm reporting the issue because I could have not noticed it, maybe something should be done when a build is ran when another build is in process. The main issue is deploying a non-working app to production without noticing it. I agree that's a very particular use case, which is very hard to reproduce. People shouldn't be building while doing modification to the source code with a watcher enabled. =D</p>