Working with open source at @snappmobile taught me what makes Swift packages truly good—beyond just working code.
Consolidated it into a 3-part checklist series: docs, dev workflow, community. All the stuff that's scattered across different resources.
Building in public, sharing the journey.
#Swift #SwiftLang #OpenSource #iOSDev #SwiftPackageManager #BuildingInPublic
Why didn't Swift have this sooner? 𝑆𝑤𝑖𝑓𝑡 𝐶𝑜𝑛𝑓𝑖𝑔𝑢𝑟𝑎𝑡𝑖𝑜𝑛 1.0 is here, bringing standardized runtime configuration to Swift projects built with SwiftPM.
🔗: https://www.swift.org/blog/swift-configuration-1.0-released/ by 𝗛𝗼𝗻𝘇𝗮 𝗗𝘃𝗼𝗿𝘀𝗸𝘆
Every application has configuration: in environment variables, configuration files, values from remote services, command-line flags, or repositories for stored secrets like API keys. But until now, Swift developers have had to wire up each source individually, with scattered parsing logic and application code that is tightly coupled to specific configuration providers.
While tuning my SDK, I added an example app as an executable target. If it uses APIs beyond what your SDK supports (.𝘱𝘭𝘢𝘵𝘧𝘰𝘳𝘮𝘴), the compiler fails. Expected.
But: any dependencies the example app uses get declared in the package config - they show up when users add your SDK. Users get frameworks they didn't ask for.
Example apps should only use the SDK they're made for. Keeps things clean.
What if your Swift packages could adapt to different build configurations automatically?
SPM Traits act as powerful feature flags, enabling conditional compilation, optional dependencies, and advanced package configurations. Think of them as the missing piece for building truly flexible, modular Swift packages that adapt to your project's needs.
🔗: https://theswiftdev.com/2025/all-about-swift-package-manager-traits/ by @tiborbodecs
Do you treat compiler warnings as errors in your Swift Packages?
A practical tutorial on how to take control of compiler warnings in Swift Packages using Swift 6.2's new settings. A must-read for anyone who loves a clean build.
🔗: https://useyourloaf.com/blog/treating-warnings-as-errors-in-swift-packages/ by @kharrison
@danielsaidi
It's curious. This consistently affected my laptop (M2) and desktop (M1), so I assumed it was widespread, but there was little commentary. It did not affect my beta-testing old laptop (Intel). So I kept my CI server on macOS 15.3 & Xcode 16.2.
But now setting up a new laptop all worked perfectly. And a new user account on the main laptop also worked. So I bit the bullet and updated the CI (M4) and it was also unaffected.
I've tried clearing #SwiftPackageManager and #Xcode caches but no effect. Not sure if it could be third party software? There are a couple of posts on Developer Forums and I filed FB16928021 during the beta.
Have there been other blogs/comments?
Oleksii Kolomiiets
Qiita - 人気の記事
Snapp iOS Weekly
Uli Kusterer (Not a kitteh)
Stewart Lynch 🇨🇦
David Davies-Payne
apfeltalk 
