Use laravel-mix for assets#801
Merged
Merged
Conversation
Move asset build process earlier, instead of moving and renaming
- Goes to nowhere in CI - Annoys when test building release locally
The release should be one made from current modules
Member
Author
|
Let's see if can get some help from There has been some past reports on the topic, but don't really see any solution: |
This allows userstyle really override css
Merged
This was referenced May 5, 2020
Member
Author
|
for future: https://github.com/iulyanp/elixir-mix-bundle |
This file contains hidden or 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
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.
Use laravel-mix for assets.
htdocs/css/main.css,htdocs/css/page.csshtdocs/js/main.js,htdocs/js/page.jsassetsmarty function{$core.rel_url}dev assets
production assets