# Package Manager exported dependencies

**URL:** <https://forums.swift.org/t/package-manager-exported-dependencies/11615>\
**Category:** Package Manager\
**Tags:** dependency-managemen\
**Created:** [April 3, 2018, 5:28am UTC](https://forums.swift.org/t/package-manager-exported-dependencies/11615 "2018-04-03T05:28:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![calebkleveter](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/calebkleveter/32/9273_2.png) [@calebkleveter](https://forums.swift.org/u/calebkleveter)\
**Post date:** [April 3, 2018, 1:36pm UTC](https://forums.swift.org/t/package-manager-exported-dependencies/11615/4 "2018-04-03T13:36:31Z")

</div>

Everything I read around the web says "don't use it, it could break any time because it's private, etc.". I agree that it could break any time, but that annotation is widely used in some Swift communities and I think a hue and cry would be raised should it be removed.

I found [this thread](https://forums.swift.org/t/exported-and-fixing-import-visibility/9415) that discusses this subject of the visibility of an import and is also the only place I have seen a Core Swift Team member discuss it. From what I read, I don't think there is too much of a concern at this point of its removal, though I could be wrong on that.

---

_[View the full topic](https://forums.swift.org/t/package-manager-exported-dependencies/11615)._