Explore switching to Webpack-only instead of Mix

[justintadlock]

I initially decided upon Laravel Mix because it was something that most of our primary group of devs agreed upon as a solid solution. It didn't have everything that everyone wanted, but it had enough for us to compromise and close out months of discussion over a build system. This was one of the biggest hurdles for even getting Mythic launched.

While Mix does everything I personally need at the moment, I believe moving to a Webpack-only solution would be beneficial in the long run because it would help developers become more familiar with the underlying technology. Mix is a layer on top of Webpack, which can sometimes hide what's going on. In some cases, that can make it harder to do things.

And, we're still waiting for Mix to catch up with the latest improvements (particularly speed improvements) in newer versions of Webpack.

I'm not convinced we need to change right away. However, I do want to open this ticket so that we can explore this option for version 2.0 or so. Or, at the very least, have some examples for others who want to go down that path for themselves in the meantime.

Right now, I'd love to see others' Webpack-only implementations.

[brettsmason]

A starting point:
https://github.com/brettsmason/luxe
https://github.com/samikeijonen/uuups/tree/dev

[saas786]

I have worked with Web Pack before using laravel mix, and I really like its simplicity.

It seems like it has progressed a lot in last couple of weeks,

released>>

https://github.com/JeffreyWay/laravel-mix/releases/tag/v3.0.0
&&
https://github.com/JeffreyWay/laravel-mix/releases/tag/v4.0.0

and let see how it goes, before switching to webpack only build.

[justintadlock]

I have to admit that seeing the Mix 4.0.0 tag makes this less of an immediate concern to me. Not being able to use Webpack 4 has been a pain point.

This ticket is not dead though. It'll likely stay open until we make a decision at some later date. It's still very much exploratory.

Related: #70