• Unity
  • UPM integration

Related Discussions
...

Hello. I would like to utilize UPM GitHub functionality to include Spine Unity to multiple of my projects with ease, also it helps clear up plugin clutters in the project's Asset folder. Howeve you didn't officially make the repo GitHub - EsotericSoftware/spine-runtimes: 2D skeletal animation runtimes for Spine. UPM compatible (has package.json and maybe asmdef)

I have to rehost it instead of forking. Since forking would fork all runtimes. Also, UPM requires the package.json to be at GitHub root, and also it cannot be a private repository. Is this possible to do this from legal standpoint? Or I must resort to local UPM? Thank you.

*edit The repo that is UPM compatible looks like this : https://github.com/5argon/spine-unity-upm

Hello,
Due to support for subdirectories being in "planned for the future" state, we first decided to give the UPM ecosystem some more time to mature before we adapt our structure to fit it. What also kept us a bit skeptical is that recursive dependencies (via UPM git urls, not via git submodules) are not yet planned to be supported.

However, we have just recently read about someone using npm's "files" field in a upm package.json manifest file (in UPM it's still undocumented, though), which could work without any restructuring. We have not yet tested it, but if anyone can confirm this works, we are more than happy to implement official UPM package support this way.

In general: If anyone has any other ideas on how we could avoid a redundant additional UPM-enabled repository with only the Unity-relevant files in it, we are happy to hear your input!
We could add 3.7-upm and 3.8-beta-upm branches where all other runtime files are removed, but this still seems somewhat clumsy.