Ask questionsHow to get auto-prefixing with vanilla Emotion?
<!-- Documentation issues are a great way for newcomers to contribute to open source projects! If you have time please consider opening a Pull Request with your documentation changes. -->
I've re-read multiple times all the different areas of the documentation that refers to vanilla Emotion usage:
https://emotion.sh/docs/introduction#framework-agnostic https://medium.com/@tkh44/emotion-ad1c45c6d28b https://emotion.sh/docs/install https://emotion.sh/docs/emotion
but I'm confused about what exactly Emotion is doing with the
css-decorated template literals and how I can get them to be auto-prefixed. In my build pipeline, I have the
autoprefixer plugin set up with PostCSS for the CSS loader, but from what I can see, Emotion does not omit any CSS.
I think it would be nice to:
Answer questions clemmy
Ah, thank you for the quick responses! So if I understand correctly, vanilla emotion should support auto-prefixing out of the box? :) We should totally be selling this feature!
My main misconception comes from: https://emotion.sh/docs/introduction#react where it says
CSS prop support - Similar to the style prop but adds support for nested selectors, media queries, and auto-prefixing.
Perhaps we should move the auto-prefixing support to the
Framework Agnostic section 😄