Seeking guidance on @_exported usage in production apps

Development Package Manager
1

I'm evaluating whether to use @_exported import in a production iOS codebase to reduce import boilerplate across a modular app with numerous SDK dependencies (Firebase, Facebook, analytics libraries, etc.).

The pattern would look like this:

swift

// UmbrellaImports.swift
@_exported import Lib1
@_exported import Lib2
@_exported import Lib3
@_exported import ...

Would it then be ok in the app to use import XXXCore everywhere or are there downsides on this?

1 Like