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 #34
Comments
Hey! Hm, interessting idea! I usally use special SASS code to do that. Is this prefixer working well? I never used such prefixer-addons. |
Autoprefixer is awesome, but I never used it on Atom. It just makes a week I'm using Atom. As you, I prefer to keep all my code clean, instead of write the prefixes by myself. It's also easier to config AutoPrefixer than to keep track of the prefixes that are really necessary and discard the old ones, even using mixins. A sample setting: {
"browsers": [
"last 3 versions",
"> 10%",
"ie 9",
"ie 8",
"Firefox ESR",
"iOS 7"
]
} I think it's a good improvement to your addon. But I really don't know if it's easier for you to use the original AutoPrefixer or @sindresorhus's package. |
Hi! I just found something that maybe could interest you: Pleeease! |
I don't use all features from Compass, but I like the cross-browser compatibility mixins. As adding Compass seems to be a bit trickier then feasible, another solution like Autoprefixer or Pleeease would be great. |
For Less there's a variant package that supports PostCSS; https://github.com/tnottu/less-postcss-autocompile |
An excellent package. Similar functionality for SCSS would be awesome. |
Just wondering if there is any movement on bringing Autoprefixer into this awesome Sass compiler? Definitely would be handy! With things like flexbox being quite popular now, it gets pretty ugly if you put in vendor prefixes into your source code manually. Thanks!! |
+1 Any chance please? |
Hi!
Please, is it possible to auto prefix the compiled file?
Thank you for the package and for your attention.
The text was updated successfully, but these errors were encountered: