We wouldn’t do it if browsers weren’t a buggy mess with the USE tag though (Chrome in particular is a dumpster fire of SVG bugs).
Also, sometime you just need to inline SVG, for example if you want some icon path fill color to change on mouse-over. Easy with inline SVG and CSS rule. Can't really do that (well) with external .svg.
Until browsers collectively get off their asses with SVG (most of these bugs are years old in their big trackers) using React for SVGs is a good workaround.
Of course it's not like svg will get removed so Why fight it...
I can see that easily solved much better, cleanly and not to mention lightweight with some CSS rather simple pre-processors in the build process.
Or is your argument that you already have a (React-based) build-process and you'd want to align this with what you have, rather than creating something new and different along-side everything else (despite the result being suboptimal)?
No, I didn't. Thanks. /s
There are many cases it's more convenient updating SVG using React.
If you try rendering, say, maps with SVG, this becomes a significant issue.
Sometimes SVG is a good fit for the graphics needed.