-
Notifications
You must be signed in to change notification settings - Fork 12k
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 not working for serving prod builds #3156
Comments
@filipesilva, So it looks like |
The conflict here is between my PR #2593 and #2852. Both creates a new instance of webpack.LoaderOptionsPlugin in the plugins array. A quickfix for now would be to simply move postcss-discard-comments into common and doing that in dev aswell. I placed it in prod only to save CPU cycles while working in dev tho. I don't think there is any webpack plugin for merging that type of config. |
I manually patch webpack-build-production.js in order to have autoprefxing on production build. I also had to add some extra params on autoprefixer because I needed to give support to Safari 7: |
@oriolcp In order to specify browser needs concerning this, you can do all of this using a browserslist file (https://github.com/ai/browserslist). No need to make any changes in the core this way |
Thanks a lot I didn't know about browserslist file. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Versions.
Repro steps.
ng serve
, the output will have various prefixed CSS properties for display: flex;ng serve --prod
, the output will only have the actual written display: flex, without any prefixes.The text was updated successfully, but these errors were encountered: