Closed ai closed 10 years ago
/cc @ianstormtaylor @MoOx
+1
There is no Autoprefixer 3.0? Every others plugins already migrated :(.
Would gladly accept a pull request ;)
@ianstormtaylor #104
Really? We need about a month to fix 2 lines? This fix can be written faster, that comment this page.
I am angry because I can’t find any reason of this delay. Latest Autoprefixer can decrease CSS size. So every big update of Autoprefixer will gives better CSS for your customers.
You could have submitted a PR instead of opening the first comment as well? There's no reason to be angry, it's just a matter of making the repository owner's job easier. And you're the best person to do that since you know Autoprefixer the best.
It's simple: everyone is working on lots of things, and I haven't personally needed any new features from Autoprefixer, so my top priority is not to upgrade to 3.0.0. Myth users aren't my "customers" because I'm not being paid to work on Myth, it's a community that works together to improve things.
Fixed in 1.2.0
.
Autoprefixer 3.0 brings two API changes:
autoprefixer-core
package for plugin development. It has no file system and CLI code and has nofs-extra
dependency.options
object:autoprefixer({ browsers: browsers })
.I recommend to everyone move to
autoprefixer-core
.