# Using standard library modules in packages

**URL:** <https://discourse.julialang.org/t/using-standard-library-modules-in-packages/128719>\
**Category:** General Usage\
**Created:** [May 5, 2025, 1:27pm UTC](https://discourse.julialang.org/t/using-standard-library-modules-in-packages/128719 "2025-05-05T13:27:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [May 5, 2025, 1:27pm UTC](https://discourse.julialang.org/t/using-standard-library-modules-in-packages/128719/1 "2025-05-05T13:27:22Z")

</div>

Hello, as result of the stlib excision effort, packages that now (Julia 1.11 ??) want to import a module from the standard library, they need to declare the corresponding package in their Project.toml, right?

---

<div class="post-metadata">

**Author:** ![palday](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palday/32/12640_2.png) [@palday](https://discourse.julialang.org/u/palday)\
**Post date:** [May 5, 2025, 4:25pm UTC](https://discourse.julialang.org/t/using-standard-library-modules-in-packages/128719/2 "2025-05-05T16:25:18Z")

</div>

Yes.

And technically they should have been doing that all along…

---

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [May 6, 2025, 1:23am UTC](https://discourse.julialang.org/t/using-standard-library-modules-in-packages/128719/3 "2025-05-06T01:23:10Z")

</div>

That’s been the case for a while now. And a couple of years ago they started requiring you to specify a separate version number for stdlib dependencies, too: [PSA: Compat requirements in the General registry are changing](https://discourse.julialang.org/t/psa-compat-requirements-in-the-general-registry-are-changing/104958)