Suggestion: Leave SVGO out of this package

You can easily add SVGO to the pipeline on Webpack, so leave it out of your package to reduce complexity.

Webpack 2 example:

{
  test: /\.svg$/,
  loaders: [
    'babel-loader',
    'react-svg-loader',
    {
      loader: 'svgo-loader',
      options: {
        floatPrecision: 2
        plugins: [{removeTitle: false}],
      }
    },
  ]
}

[pluma]

Just an FYI: I’ve had react-svg-loader blow up because an SVG contained CSS (which contains curly braces which JSX treats specially) so this approach is pretty error prone.

[boopathi]

1, 2(remove comments and doctype) and also fix up invalid XML and 3 - is exactly what SVGO already does. Since we already use SVGO, it’d be good and easy just to expose the API.