Just noticed that the way the framework is distributed through SPM is very inefficient. To resolve the dependency, the package manager downloads the whole repository with lots of uneeded stuff resulting in >100mb of data.
This was not noticeable in our setup as we proxy all the remote repos which local packages. However, for many people who only rely on remote packages this should be a major PITA.
To comply with best practices you should provide the xcframework as a binary artifact distributed as separate repo with Package manifest linking to such artifact. I would even recommend to go as far as providing xcframeworks for speicific platforms, such as iOS only etc, as what you provide today is insanly huge artifact around 40mb in size.
Hey all,
Just noticed that the way the framework is distributed through SPM is very inefficient. To resolve the dependency, the package manager downloads the whole repository with lots of uneeded stuff resulting in >100mb of data.
This was not noticeable in our setup as we proxy all the remote repos which local packages. However, for many people who only rely on remote packages this should be a major PITA.
To comply with best practices you should provide the xcframework as a binary artifact distributed as separate repo with Package manifest linking to such artifact. I would even recommend to go as far as providing xcframeworks for speicific platforms, such as iOS only etc, as what you provide today is insanly huge artifact around 40mb in size.