I've found some posts that talk about the possibility of svg's in Spine, but none that make a clear distinction between the two (as I see it) possible implementations that could be done.
1) import svg's for use as meshes in spine, but export rasterized assets
This is the simpler, more broadly useful implementation.
It just lets us not have to worry about resolution until it's time to export from Spine, rather than before we import into Spine.
2) export svg animations
This is the more powerful, but less frequently useful and more difficult to implement possibility.
The animations would probably only be useful with this Unity plugin that's been mentioned in other threads. https://assetstore.unity.com/packages/tools/sprite-management/svg-importer-38258
I think at least the the first option should be developed. I believe it's fairly common for assets that are to be used as meshes in animations to start out as vector graphics. The ability to import these vectors into Spine without rasterizing would:
a) prevent having to import higher resolution assets when you find out you need to support higher resolutions
b) reduce Spine projects' disk usage