SPM Package Resolution Size Growing With Each Release

[matcartmill]

Hello, folks!

Currently in order to use SPM with UID2 the clone, as of April 14, 2025, is nearly 450MB. The bulk of this size is due to committing Carthage binaries in the repo itself. Even though SPM modules by default with only use the files listed in Sources, SPM still needs to clone the entire repo first and then works to resolve the version you want/need.

As you can imagine, once you are in a place without extremely fast internet (or dealing with CI/CD virtual images) downloading 450MB for a single library becomes problematic, especially when 99% of the downloaded content is not relevant to building this library with SPM.

If vending Carthage binaries from this repo is a requirement, is it possible to do what the Airbnb team does with the "Lottie" framework, and keep a secondary repository that simply lists a lightweight package file that points to an xcframework in the main repository?

See: https://github.com/airbnb/lottie-spm

If you have other ways to protect the size of the repo, I would love to understand more about how that can be achieved.

Attached a screenshot for good measure.

Thanks!

[matcartmill]

@sunnywu I see you asked someone to tag you in a previous issue, so just wanted to do the same here for visibility.

Thanks!

[sunnywu]

Hi @matcartmill,

Thank you for your question. We will discuss this internally and respond back at the earliest

[dcaunt]

Thanks again for reporting this issue. It is resolved by #75 and shipped in Release v1.7.11. The approximate checkout size is now 2.2Mb.