Lev Solntsev

Yeah, it would be nice, but it's a complex topic. There a lot of optimizers with different optimizations degree and execution time, also they're a hardly depend on image type...

There is no special interface for external plugins, except you can pass functions within config object like ```js { "plugins": [ /* ... list of SVGO plugin options ... */...

There is no JS-based bitmap image optimizers I'm aware of. It's even doesn't make sense. It'd same as binary optimizers but with drawbacks.

Yep, but I don't understand your point. What's next?

I haven't made a decision yet. Not sure about the plugin. Need some time to consider.

Just as any stripping—minimize number of bytes, increase informational density.

Why? It's removed only when `width` and `height` attributes are present and equal to, so no information is lost. Finally, one can turn it off if needed.

@robertknight that's incorrect usage, nothing to do with SVGO. Of course if you rewrite `width` and `height`, you'll get an error, no matter in which way.

SVG is an image which may have properties like `width` and `height`. Without `viewBox` attribute it has value equal to `0 0 width height`. So if you change size in...

I understand the issue, sometimes 'viewBox' is really valuable, but it's not a good idea to dictate disabling default optimization by minority of users. Most users are ok with it...