A Nervous Smoothie from the Swift Package Registry
summary
Explains how a team used Swift Package Registry to package only the needed artifacts from Swift Package Manager repositories, avoiding unnecessary files and unexpected transitive-version updates across four large projects. Describes creating lightweight, stable archives (registry packages) so projects consume just the required bundles instead of full Git repos with extraneous content.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:06Target audience
- 2:09Swift Package Manager
- 4:20Dependency resolve issues
- 7:34Package Registry emergence
- 8:36Package Registry
- 10:50Registry development history
- 15:37How Package Registry works
- 18:29Using Registry in practice
- 21:44Git versus Registry
- 23:08Speed and convenience comparison
- 26:42Registry operational nuances
- 31:51Internal Registry benefits
- 34:22Project usage example
- 37:51Binary packages workflow
- 40:02Summary and recommendations
- 41:30Learning resources
- 42:33Q&A
related talks
33mScaling Swift Development
44mSwift Packages - Dependency Management of the Future
26mKeeping Things Modular With Swift Package Manager
48mSwiftPM — Frameworks Instead of Coffee
39mModularization techniques from monolithic to multi-packages app
19mSwift to the cloud in a single step
01h 00mHow to Build Modularity with SPM and a Monorepo Without Going Gray
24mThinking Outside the Box with Swift Package Manager