<p dir="auto">Currently, the example 'with-typescript' is using an ugly 'concurrently' to run asynchronously with next.js.<br>
I tried to modify the webpack loaders but no hope,  next.js required files be in filesystem/.next folder, not memory. Now I can't use my lovely CoffeeScript for API construction<g-emoji class="g-emoji" alias="confounded" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f616.png">😖</g-emoji>. I have to launch external project for that.</p>
<p dir="auto">As mentioned in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="202752614" data-permission-text="Title is private" data-url="https://github.com/vercel/next.js/issues/867" data-hovercard-type="issue" data-hovercard-url="/vercel/next.js/issues/867/hovercard?comment_id=277801396&amp;comment_type=issue_comment" href="https://github.com/vercel/next.js/issues/867#issuecomment-277801396">#867 (comment)</a> and <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="198372953" data-permission-text="Title is private" data-url="https://github.com/vercel/next.js/issues/627" data-hovercard-type="issue" data-hovercard-url="/vercel/next.js/issues/627/hovercard?comment_id=271184919&amp;comment_type=issue_comment" href="https://github.com/vercel/next.js/issues/627#issuecomment-271184919">#627 (comment)</a>, it sounds possible to use Webpack universally. There's e.g the <a href="https://github.com/halt-hammerzeit/universal-webpack"><code class="notranslate">universal-webpack</code></a> package which might help, and this <a href="http://jlongster.com/Backend-Apps-with-Webpack--Part-I" rel="nofollow">article</a> gives some tips and an example.</p>
<p dir="auto">If it can be done efficiently, having a universal Webpack sounds like a great way to reduce the complexity of the Next.js codebase and would allow users to load any Webpack plugin they need?</p>
<p dir="auto">What's Next.js' team's opinion on this, does it make sense and should it be investigated?</p>