-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overhaul Mix build #2524
Overhaul Mix build #2524
Conversation
@williamjallen, how supported is the "hot reloading" in this MR? I'm running into an issue when using it, but don't want to request changes if there are still things coming. |
@josephsnyder Hot reloading is still not usable. This PR is pretty much just a refactor of the build process so I can more easily tackle problems like hot reloading in the future. The main improvement in this PR is the improved cache busting behavior. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Once rebased, it should be added to the merge queue!
All files will now be overwritten, so no need to delete the old build files first.
a4b3513
to
003a3e4
Compare
After #2524 we started seeing 404 errors when attempting to load 3rdparty.min.js and legacy_1stparty.min.js for Angular and Vue pages. The solution is to meticulously wrap all our calls to mix() in asset().
This PR is the first of several aiming to clean up our frontend website build process and overall asset structure. This PR overhauls the Mix build script, leading to better cache busting behavior for some assets.
Future work includes: