Separate mix file for frontend development #18
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
October 5, 2017 12:43
Closed
Gberzi01
pushed a commit
to Gberzi01/arbory
that referenced
this pull request
Feb 7, 2020
Rename laravel translatable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue and discussion here: #7
I've modified ./webpack.mix.js to simply require arbory's webpack.mix.js, which depending on the value of an env parameter either configures mix to compile admin assets, or skips all that and requires ./webpack.mix.front.js to compile frontend assets.
arbory:installis updated to compile admin assets.webpack.mix.front.js is generated from stub with simple defaults only if it doesn't already exist in root directory.