-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
Autoprefixer comments are stripped out when using sass-loader #638
Comments
Indeed - because CSS minification is handled with |
People can opt-out from using the
That point may cause a bigger issue though, because Dart Sass does not seem to support
We'll have to be careful about setting options that are not directly handled by the loader since they are passed to the chosen implementation which may or may not support them. |
I've created a PR #639. Any remarks are welcome! |
…rikx) This PR was squashed before being merged into the master branch (closes #639). Discussion ---------- bug #638 sass-loader should not do css minification Fixes a BC break from the sass-loader minifying the CSS which is already done with mini-css-extract-plugin. I chose to use outputStyle 'expanded' so it's also compatible with Dart Sass. Commits ------- f55fb90 Adapt test for new sass-loader config ae5fea1 bug #638 sass-loader should not do css minification
Any reason for this issue not being closed? |
@garak I think we simply forgot to close it since most of the time it's done automatically thanks to the It should be OK with the latest version of Encore, if that's not the case feel free to reopen. |
With version 7.3.0 of sass-loader, compression is also done during the production build process. Apparently, this happens before autoprefixing kicks in (postcss-loader), which causes the necessary grid comments (
/* autoprefixer grid: on */
) to be removed, thus preventing Grid autoprefixing for IE during production.I have found 2 possible fixes:
/*! autoprefixer grid: on */
enableSassLoader(function (options) { options.outputStyle = 'expanded'; })
Personally, the 2nd fix seems to be the best solution, but maybe this can be provided by default when compression is already done by postcss-loader?
The text was updated successfully, but these errors were encountered: