Kevin N.
Kevin N.
I also agree with you, viewBox is very important for the scaling specially for web developper. In previous versions of svgo, removeViewBox was false by default. You should reconsider setting...
> Perhaps readme should be updated. SVGO mostly optimize without a _visible_ affect on rendering result. One of the most effective optimizations is reducing float numbers precision. Usually, one will...
> > You are wrong, removing the **viewBox affects rendering**. Please read the viewBox documentation on mozilla and check the example, it's the same svg used three times with three...
Hi, If you implement options to configure how metadata are added, it could be great if we can have an option to remove the metadata part from the payload (at...
I am facing the exact same issue with cog 0.16.1, it's reproductible with many websites. @CharlieBra7o Did you find a solution? @aperezdc Do you have an idea? Thanks!
@CharlieBra7o Thanks for the update! We have the same issue and we are also trying to find a solution. This issue seems to be the same as [this one](https://github.com/WebPlatformForEmbedded/WPEWebKit/issues/952).
So **forwardRef** and **"functions": "defaultArguments"** are just incompatible? There is no workaround?
it is relevant except if you already use https://github.com/umijs/babel-plugin-import
I have the same issue, even if the plugins array is empty, it fails.
> Raised this as bug in chromium: https://issues.chromium.org/issues/330175031 Thank you for raising it! It seems to be a regression introduced in v122, they are investigating the issue.