CSS Autoprefixer support #536
Open
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
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.
This is adding Autoprefixer support which is required for using Bootstrap 4.
I think there is some bug with awestruct because I needed to write the
fix_encodingmethod. I found out that CSS files with non-ascii charactersseem to be loaded as ASCII_8BIT which later breaks the
Autoprefixerexecution.This might be the case only when ExecJS is using Node.js backend. In any case
it would be better to handle this in awestruct core instead of in transformer.
That is because
therubyracerbackend is not reliable and deadlocks in threadedenvironments. Please see sstephenson/execjs#205