-
-
Notifications
You must be signed in to change notification settings - Fork 188
Consider switching compressor #94
Comments
Or maybe we should just get rid of the compressor in cssnext. |
it's more a clone of cssnext than a compressor ? |
Humm not from what i see in the first place. Only postcss-calc looks duplicated. |
you're right. There are many optimization, code cleanup. So why not. What's your idea ? Only use instead of |
All of that? :)
|
lol ok 👍 |
Two things:
|
Maybe @ben-eb can helps us on that ? |
Sure; the architecture is similar to cssnext in that you can disable processors, although some of those I opted to not disable as they are safe optimisations. e.g since postcss-pseudoelements v2, the single colon syntax of before and after is supported across all browsers so is safe to minify. Of course, I can add the option to disable these if you would like. |
It's not necessary since we are using this plugin only to ensure ie8 compat (so if IE 8 is not in the scope, we won't enable it). |
yes, but And what do you think about |
@MoOx @magsout I think you are better to wait until this attribute selector bug is fixed before you migrate. 😄 https://github.com/ben-eb/postcss-minify-selectors/issues/2 |
@magsout you write |
LGTM |
https://github.com/ben-eb/cssnano
The text was updated successfully, but these errors were encountered: