-
Notifications
You must be signed in to change notification settings - Fork 47
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 disabled in SASS preset in Assets #14
Comments
@tomaszbujnowicz ah interesting, thanks for the issue! Yeah we should be able to fix that. The idea is for these presets to be plug-n-play, so def want to add all the bells and whistles that most people need (like autoprefixer). The SASS preset is here. I imagine we just need to add a bit of config in there. |
I think it would be definitely cool to be able to configure webpack inside Slater to use any other CSS framework e.g. https://tailwindcss.com/ |
Ok, I think the best way would be to include postcss.config.js in the theme folder or include these postcss settings directly in slater.config.js Quick and dirty workaround for now:
The whole block should look like:
Please note that ideally we should use postcss.config.js in order to handle supported browsers. |
@estrattonbailey has there been any thought on allowing extension of the default webpack config? |
@all-contributors please add @tomaszbujnowicz for code |
I've put up a pull request to add @tomaszbujnowicz! 🎉 |
It seems that autoprefixer is disabled when switching to SASS preset:
Is there any way that we can enable it through slater.config.js?
Or any other way.
I couldn't find that option anywhere.
Hope you can help guys ;)
The text was updated successfully, but these errors were encountered: