cocoapods-to-spm

To migrate an iOS Capacitor project from CocoaPods to Swift Package Manager, you analyze current pod usage, map dependencies to SPM equivalents, clean up the Podfile, and configure Xcode package dependencies. A hybrid approach can keep Capacitor core under CocoaPods while migrating other libraries to SPM.

Yes, you can use a hybrid workflow that keeps the Capacitor core under CocoaPods while migrating third-party libraries to Swift Package Manager. This approach allows gradual migration of iOS dependencies without breaking the existing Capacitor build configuration.

Removing CocoaPods from an Xcode project involves cleaning up the Podfile, removing the Pods directory, and configuring Xcode to use Swift Package Manager dependencies. The workflow ensures dependency analysis maps existing pods to valid SPM equivalents before finalizing the build setup.

Capacitor supports Swift Package Manager for iOS dependencies through a hybrid workflow, allowing you to migrate third-party libraries to SPM while maintaining the Capacitor core under CocoaPods. This modernizes dependency management across the iOS build without fully abandoning existing pod integrations.

A key limitation is that the Capacitor core itself typically remains under CocoaPods, meaning a full removal of CocoaPods may not be possible for all Capacitor iOS projects. The hybrid approach requires careful dependency analysis to ensure third-party libraries have valid SPM equivalents before migration.