# Package does not have ... in its dependencies, but it does

**URL:** <https://discourse.julialang.org/t/package-does-not-have-in-its-dependencies-but-it-does/22017>\
**Category:** General Usage\
**Tags:** package, development\
**Created:** [March 19, 2019, 5:30am UTC](https://discourse.julialang.org/t/package-does-not-have-in-its-dependencies-but-it-does/22017 "2019-03-19T05:30:15Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![singularitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/singularitti/32/17678_2.png) [@singularitti](https://discourse.julialang.org/u/singularitti)\
**Post date:** [March 29, 2019, 5:00am UTC](https://discourse.julialang.org/t/package-does-not-have-in-its-dependencies-but-it-does/22017/5 "2019-03-29T05:00:22Z")

</div>

Thank you for your reply. I am just curious about why `Project.toml` is not enough. Because I saw

> 1. When everything is working the dependencies are computed from the `Project.toml` not from `REQUIRE` . You don’t need the `REQUIRE` file anymore.

from [here](https://discourse.julialang.org/t/recommended-way-to-migrate-an-existing-package-to-pkg3/11560/2).

---

_[View the full topic](https://discourse.julialang.org/t/package-does-not-have-in-its-dependencies-but-it-does/22017)._