# The adoption of \`import FoundationEssentials\` throughout the package ecosystem

**URL:** <https://forums.swift.org/t/the-adoption-of-import-foundationessentials-throughout-the-package-ecosystem/84112>\
**Category:** Development\
**Created:** [January 13, 2026, 4:28pm UTC](https://forums.swift.org/t/the-adoption-of-import-foundationessentials-throughout-the-package-ecosystem/84112 "2026-01-13T16:28:17Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![0xTim](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/0xtim/32/27968_2.png) [@0xTim](https://forums.swift.org/u/0xTim)\
**Post date:** [January 13, 2026, 5:34pm UTC](https://forums.swift.org/t/the-adoption-of-import-foundationessentials-throughout-the-package-ecosystem/84112/4 "2026-01-13T17:34:46Z")

</div>

Related discussion here - [FoundationEssentials on Darwin?](https://forums.swift.org/t/foundationessentials-on-darwin/74856)

I think the goal here is the right one. I think it’s going to be very difficult to achieve without the tooling in place to make it a usable developer experience

---

_[View the full topic](https://forums.swift.org/t/the-adoption-of-import-foundationessentials-throughout-the-package-ecosystem/84112)._