Code Organisation for Julias
Julia code organisation is how larger programs are structured: modules for namespaces, files joined with include, and packages created with Pkg.generate or PkgTemplates. It sits in the Projects stage and covers exports, dependencies and versioning so that your code can be reused by other people and projects.
Stage: Projects · Part of the Julia roadmap · Last reviewed 19 November 2026
What to learn in Code Organisation
- Wrap related functions in a module and control what is exported
- Split a module across files using include
- Create a package skeleton with src, test and Project.toml
- Declare dependencies and compatibility bounds in Project.toml
- Use the revise workflow to edit code without restarting Julia
Code Organisation interview questions
What is the difference between using and import in Julia?
using brings the module's exported names into scope so you can call them directly, while import brings in only the module name, so you refer to functions with a prefix, and it is needed to extend functions by adding methods. Both load the package.
What does Project.toml contain?
Project.toml lists the package name, unique identifier, version, direct dependencies and their compat bounds. A Manifest.toml beside it records the full resolved versions of every dependency, which lets an application reproduce its exact environment.
Where Code Organisation fits in the Julia roadmap
Code Organisation belongs to the Projects stage (advanced level). Structure real work.
Other units in this stage
Back to the full Julia roadmap