# Single module vs. submodules in a project

**URL:** <https://discourse.julialang.org/t/single-module-vs-submodules-in-a-project/55361>\
**Category:** New to Julia\
**Tags:** performance, modules, code-organization\
**Created:** [February 15, 2021, 11:23pm UTC](https://discourse.julialang.org/t/single-module-vs-submodules-in-a-project/55361 "2021-02-15T23:23:33Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![MA\_Laforge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ma_laforge/32/385_2.png) [@MA\_Laforge](https://discourse.julialang.org/u/MA_Laforge)\
**Post date:** [February 16, 2021, 11:54pm UTC](https://discourse.julialang.org/t/single-module-vs-submodules-in-a-project/55361/16 "2021-02-16T23:54:23Z")

</div>

> [@erans](#):
>
> I’m actually leaning a bit more towards simply `] activate <path to my project>` which should still make `using MyPkg` possible, no?

If you go that route, you might prefer creating a simple shell script to launch julia using the `--project /path/to/my/project` argument.

You can also check out my module “ConventionalApp.jl”:  
→ [[ANN] ConventionalApp.jl ](https://discourse.julialang.org/t/ann-conventionalapp-jl/52390)

You don’t HAVE to use ConventionalApp.jl. It is basically just a utility module to help you create bash files, etc. But it gives you _ **a** _ solution on how conventional applications can be “generated”/launched in a somewhat practical manner.

Note that ConventionalApp.jl also cleans up the `LOAD_PATH` (removes unnecessary `"@v#.#"` “project” from the environment stack).

---

_[View the full topic](https://discourse.julialang.org/t/single-module-vs-submodules-in-a-project/55361)._