Closed joseluisq closed 9 years ago
confirm!
Task
autoprefixer: {
options: {
browsers: ['> 1%', 'last 2 versions', 'Firefox ESR', 'Opera 12.1'],
map: true,
inline: false,
sourcesContent: false
},
dist: {
files: [{
expand: true,
cwd: '<%= config.app %>/',
src: '{,*/}*.css',
dest: '<%= config.app %>/'
}]
}
},
Output
+1
+1
+1
Just move to grunt-postcss, because it is more official way to use Autoprefixer.
@ai Great! So this case I think you may to add to README.md
some explaination about this and the official link to grunt-postcss.
@joseluisq Autoprefixer’s README.md
has link only for grunt-postcss ;).
@ai sure
In general, do you recommend to use grunt-postcss
instead grunt-autoprefixer
right?
If It's true, Is grunt-autoprefixer
deprecated?
@joseluisq yeap, I recommends grunt-postcss
.
But I can’t deprecate grunt-autoprefixer
beause it is not my project.
@ai I understand now I will refer to grunt-postcss for official way. Thanks :+1:
@nDmitry this issue is not closed yeat, because you didn’t display result.warnings()
.
BTW, PostCSS Runner Guidelines is highly recommended for Autoprefixers plugins too.
@ai do you think I should deprecate this plugin in favour of grunt-postcss?
@nDmitry Yeap, grunt-postcss updates faster and it is better for ecosystem. And you need to maintain only one project.
@ai so be it)
Ok, guidelines are passed too.
Last version is v3.0.0