These are cool optimizations, though can be a bit harder to read, but it brings up svgo and svgo is a very flawed tool. When optimizing SVGs should 99% of the time choose scour (or something else) over svgo. svgo will strip out the license and metadata info is coupled as “editor data” by default, which can pose legal issues, because their creator thinks smallest size is always the optimal goal, even if it leads to rendering issues too (look at how 40% bugs are in React’s svgr are svgo-related). Even if you do as the author says and read the manual and turn off the the aggressive defaults, due to dependency chains you sometimes can’t even configure the settings anyhow because a tool was being helpful in including it.
These are cool optimizations, though can be a bit harder to read, but it brings up svgo and svgo is a very flawed tool. When optimizing SVGs should 99% of the time choose
scour
(or something else) oversvgo
.svgo
will strip out the license and metadata info is coupled as “editor data” by default, which can pose legal issues, because their creator thinks smallest size is always the optimal goal, even if it leads to rendering issues too (look at how 40% bugs are in React’s svgr are svgo-related). Even if you do as the author says and read the manual and turn off the the aggressive defaults, due to dependency chains you sometimes can’t even configure the settings anyhow because a tool was being helpful in including it.