Quick Start

This page walks through a first analysis in the web UI.

Open the Analysis Task tab in the right drawer. Enter the path you want to analyze, or click Browse... to pick it from the file system.

Analysis Task

Analysis Task

Analysis Path

/absolute/path/to/project

Directory = project-aware by default; File = self-contained by default.Project Root

/absolute/path/to/project

Leave this empty for self-contained single-file analysis. Fill it manually if you want project-aware analysis for a single file.

After the path is set, click Run Analysis.

If Analysis Path points to a directory, DependencyAtlas detects the project root automatically and shows it in Project Root.

If Analysis Path points to a single file, DependencyAtlas treats that file as self-contained by default. Top-level code outside explicit module ... end blocks is treated as Main. To analyze a single file with package or project context, fill in Project Root manually.

For a predictable first run, try test/fixtures/DebugFixturePkg. It is small, local, and covers common graph scenarios such as overloads, stdlib calls, package calls, and macro-related cases.

After analysis completes, small graphs open directly in the canvas. The result should look roughly like this.

1. Initial method view

src/DebugFixturePkg.jl

src/stdlib_cases.jl

run_all_demos

stdlib_overloaded_ logging_demo

base_overloaded_ length_demo

2. Path highlighted

src/DebugFixturePkg.jl

src/stdlib_cases.jl

run_all_demos

stdlib_overloaded_ logging_demo

base_overloaded_ length_demo

3. Reachability mode

src/DebugFixturePkg.jl

run_all_demos

base_overloaded_ length_demo

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.

Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

Click a node, for example base_overloaded_length_demo, to highlight related graph paths.

Click the same node again. Its border will turn magenta, which means you have entered reachability mode.

In reachability mode, only the nodes on that node's path are shown. Reachability depth is controlled by Reachability Depth in the Graph Explorer panel, and the displayed call direction is controlled by Reachability Direction.

Click empty space to clear the current selection. Use Exit Reachability Mode from a node's right-click menu to exit the reachability mode. Double-click empty space to reset the canvas and viewport.

Source Navigation

Right-click any method node to open its definition from the node context menu.

run_all_demos

Run JET View

Open in VS Code

Open with system default

When a supported editor launcher is detected, Open in ... opens the file directly at the method's source line. Supported editor families include Cursor, VS Code, VSCodium, Sublime Text, PyCharm, and IntelliJ IDEA.

Troubleshooting

The backend or frontend port is already in use

If something is already listening on 8099 or 5174, stop the conflicting process or restart the relevant service with a different port in your local environment.

The UI rejects the analysis path

Analysis Path must point to a local absolute path on the same machine as the backend.

How Project Root works

• If Analysis Path is a directory, DependencyAtlas detects the project root automatically.
• If Analysis Path is a single file, DependencyAtlas does not scan upward for Project.toml by default.
• For single-file analysis, top-level code outside explicit modules is treated as Main.
• If you want project-aware single-file analysis, set Project Root manually.

The UI cannot analyze anything

If you are using the default setup, make sure the backend is running and static serving is enabled.

If you are using the frontend development server, make sure both services are running:

• the Julia backend
• the web frontend

In both cases, analysis requests still go through the backend.

Need Help?

If you have questions, please open an issue on the project's issue page.