Closed ai closed 8 years ago
Yeap, but seems like it has some issue.
I'm doing the same as gulp-postcss: https://github.com/postcss/gulp-postcss/blob/8414a14c95f7c76bef8546ad6383c6f7678076f5/index.js#L63-L65
I wish there was a way (an option) to silence the warnings.
@kentmw That would be a request to Autoprefixer, not this plugin.
@sindresorhus I don't think so. I followed your link: https://github.com/sindresorhus/gulp-autoprefixer/blob/8cc62f4fa3c8bc8ab1efe2c59fe7c13ee5c7b652/index.js#L31-L35 and you are the one logging it out. We just need to add a flag for this plugin to not log it out, right?
It only logs if there are warnings: https://github.com/sindresorhus/gulp-autoprefixer/blob/8cc62f4fa3c8bc8ab1efe2c59fe7c13ee5c7b652/index.js#L33 It should be up to Autoprefixer not to emit any.
It's not Autoprefixer that is logging it. They have a nice way to retrieve warnings if you want them. This plugin is actively going out, grabbing them, and printing them. Autoprefixer isn't printing them. They just silently generate warnings.
Ok. I'm not interested in having such option as I think it belongs in Autoprefixer. Your way, every consumer have to manually implement such option instead of just Autoprefixer.
Right now Autoprefixer generates a lot of really important warnings.
But seems like users do not see them: https://github.com/postcss/autoprefixer/issues/602#issuecomment-168789444