# Notebook-specific target/Project.toml (similar to test)

**URL:** <https://discourse.julialang.org/t/notebook-specific-target-project-toml-similar-to-test/125972>\
**Category:** General Usage\
**Tags:** question, pkg\
**Created:** [February 17, 2025, 12:45am UTC](https://discourse.julialang.org/t/notebook-specific-target-project-toml-similar-to-test/125972 "2025-02-17T00:45:50Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![brunompacheco](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/brunompacheco/32/209375_2.png) [@brunompacheco](https://discourse.julialang.org/u/brunompacheco)\
**Post date:** [February 19, 2025, 6:22pm UTC](https://discourse.julialang.org/t/notebook-specific-target-project-toml-similar-to-test/125972/4 "2025-02-19T18:22:03Z")

</div>

Although I wish I could take the target approach, I’m currently keeping the separate Project.toml file, as suggested by @danielwe.

In case it’s useful for anyone facing the same challenge, I indeed added the parent package as a development dependency, and to access its dependencies I just do `using A.B` (found out about that [here](https://discourse.julialang.org/t/how-to-add-all-dependencies-of-a-package-to-global-environment/19725/8)).

---

_[View the full topic](https://discourse.julialang.org/t/notebook-specific-target-project-toml-similar-to-test/125972)._