-
Notifications
You must be signed in to change notification settings - Fork 6
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
Document auto-prefixer? #3
Comments
Use Autoprefixer ("everybody" here and there already do this). The plugin in this repo is just an experimental proof-of-concept goody which most likely will be replaced by some autoprefixer-wrapper plugin after Less 2.0 is released (that coming Less version is what all this less-plugins thing is about). |
Ok - but how does one use Autoprefixer in development (sans grunt)? I looked at it earlier and it looks like it's a post-processor - I'm just prototyping something and don't want to use grunt and all that jazz right now. I guess I thought that this version in this repo might satisfy that requirement. |
Edit: sorry I mistunderstood you at first. It all depends on how you define "development". Setting up a grunt project for prototyping is a matter of two minutes (as soon as you did that once). And if by "development" you mean just something like "I use less.js in a browser" use -prefix-free then. |
Ah, yep, and thanks - I think I should be using prefix-free here and not less for this. I do abhor the syntax swap to macros. In any case, I do think this directory could still use a README stating that this is not for use (yet) or whatever. Thanks for the pointer! |
auto-prifixer removed |
I just came across this repo while researching mixins to do prefixing..
Maybe this is better than what I found?
It would be cool to see this doc'd.
The text was updated successfully, but these errors were encountered: