title: Laravel Mix build process scalable up to lots of (50+) themes
body: <p><strong>Is there a standard way to scale Laravel Mix to support a build process of 50+ different frontend themes?</strong></p>
  
  <p>I'm simply running <code>npm run dev</code> and <code>npm run watch</code> currently with four different themes in my webpack.mix.js file, and that goes through and builds/watches all of those themes at once, but I fear performance is going to break down when we go to scale. Ideally I would like to be able to only build/watch themes one at a time, e.g. <code>npm run dev --theme:some-site</code> or <code>npm run watch --theme:another-site</code></p>
  
  <p>Here's what my webpack.mix.js is eventually going to look like at this rate if I don't change anything:</p>
  
  <pre><code>const mix = require('laravel-mix');
  
  // Parent Theme
  mix.js('resources/[parent-theme-folder]/assets/js/app.js', 'public/[parent-theme-folder]/js/')
    .sass('resources/[parent-theme-folder]/assets/scss/app.scss', 'public/[parent-theme-folder]/css/')
    ;
  
  // Client 1
  mix.js('resources/[child-theme-1-folder]/assets/js/app.js', 'public/[child-theme-1-folder]/js/')
    .sass('resources/[child-theme-1-folder]/assets/scss/app.scss', 'public/[child-theme-1-folder]/css/')
    ;
  // Client 2
  mix.js('resources/[child-theme-2-folder]/assets/js/app.js', 'public/[child-theme-2-folder]/js/')
    .sass('resources/[child-theme-2-folder]/assets/scss/app.scss', 'public/[child-theme-2-folder]/css/')
    ;
  ...etc...
  // Client 47
  mix.js('resources/[child-theme-47-folder]/assets/js/app.js', 'public/[child-theme-47-folder]/js/')
    .sass('resources/[child-theme-47-folder]/assets/scss/app.scss', 'public/[child-theme-47-folder]/css/')
    ;
  </code></pre>
  
  <p>Any suggestions? Thanks!</p>
  
  <p>--</p>
  
  <p>Some more info on our setup, if it helps...</p>
  
  <p>We're using a parent/child theme package - <a href="https://github.com/igaster/laravel-theme" rel="noreferrer">igaster/laravel-theme</a> - to manage multiple frontends in one Laravel project. Essentially, we have 4 types of website products, and 20-30 clients that all have their own instance of up to 4 of those products. They each have their own child theme that extends the parent theme for that product to add any custom layouts, styles, views, etc. We felt one Laravel project was going to be easier to manage than setting up 20-30 different Laravel projects for each client, especially when it came to managing maintenance and updates.</p>