You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the opening this issue and linking to the Webpack library, @elliottregan. ✨
One of the reasons for allowing custom transformations of SVGs is to keep the core code simple and easy to maintain, while allowing individual users to depend on third-party SVG optimizers if they choose.
Another strategy, involving even less runtime complexity, would be to optimize SVGs separately from this library, perhaps as part of the asset pipeline or other build/deploy step, which could then be cached at boot time.
I'd be happy to help you get either or both of these strategies working but I'm not convinced that adding extra SVG optimization to the core of this library is a worthwhile feature.
Removing comments is good, but more optimization features would be nice, too.
Similar concept for Webpack: https://github.com/webpack-contrib/svg-inline-loader
The text was updated successfully, but these errors were encountered: