Analysis

Analysis Issues

No Files Found / Empty Graph

Symptoms: “0 files analyzed”, empty import graph, no metrics computed.

Causes & solutions:

1. Wrong directory:

   pwd
   arxo analyze --path /path/to/project

2. Excluded by patterns — Check .arxo.yaml; avoid exclude: ["**/*"]. Use data.import_graph.exclude and fix overly broad exclusions.

3. Unsupported file types — Arxo parses .ts, .tsx, .js, .jsx, .mjs, and .py. Ensure you have source files in these languages.

4. node_modules — Exclude in config:

   data:
     import_graph:
       exclude: ["**/node_modules/**"]

---

Analysis Too Slow

Symptoms: Analysis takes >5 minutes on small projects.

Solutions:

1. Exclude test/build directories:

   data:
     import_graph:
       exclude: ["**/test/**", "**/tests/**", "**/dist/**", "**/build/**"]

2. Use caching — First run is slow; subsequent runs use cache. Ensure cache is not disabled.

3. Clear corrupted cache:

   arxo cache clear

---

High Memory Usage

Symptoms: Process killed, OOM errors.

Solutions:

1. Exclude large dependencies (e.g. node_modules, vendor).
2. Analyze in parts: arxo analyze --path ./frontend and arxo analyze --path ./backend.

---

Parsing Errors

Error: “Failed to parse file: src/example.ts”

Causes & solutions:

1. Invalid syntax — Fix with native tools: tsc --noEmit, python -m py_compile file.py, cargo check.
2. Unsupported syntax — Exclude problematic files in config.
3. Encoding — Ensure files are UTF-8: file -I src/example.ts.

Next steps

• Troubleshooting — Overview
• Policy & Config — Violations and config