Hiding internal product dependencies from consumers in a Swift package

[SDGGiesbrecht (Jeremy David Giesbrecht)]

@Saklad5

Is there a way around this?

Not at the moment. This thread has a little more information:

How to privatize dependencies in Swift Package Manager?

Implementation‐only imports only prevent a dependency from being forwarded through the import statement. // ModuleB import CModuleA // ModuleC import ModuleB // Implicitly got “import CModuleA” too. // ModuleD @_implementationOnly import CModuleA // ModuleE import ModuleD // Hasn’t implicitly imported CModuleA. At the moment, SwiftPM does nothing to enforce that import statements are also mentioned in the manifest. All dependencies—both direct and transitive—end up in the import and linker…