You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AST extractor drops imports_from edges for some source files #414
All 8 target files exist as nodes in the same graph (they appear in community listings with their own stems), so this isn't a missing-corpus issue.
Counter-example in the same run:backend/api/src/models/enums.mjs is an exports-only file, and the graph correctly shows cross-file edges between it and decision.model.mjs / candidate.model.mjs (resolved via those model files importing ../enums.mjs). So the import resolver handles some ../sibling.mjs cases, just not consistently.
Expected
Each relative import ... from "./foo" or "../foo" statement should produce an imports_from edge whenever the target file is present in the corpus.
Impact
feedback.model.mjs and session.model.mjs appear as degree-0 orphans in GRAPH_REPORT.md despite being actively imported from run-seed.mjs. This inflates the weakly-connected-nodes count and breaks reverse-lookup queries like "which files use session.model.mjs?"
Environment
graphifyy 0.4.18 (via pipx)
Python 3.12.3 on Ubuntu-based Linux (kernel 6.17)
Invocation: /graphify . via the Claude Code skill, default pipeline
Corpus: 75 files (27 code, 45 docs, 3 images)
Happy to share the full graph.json or construct a minimal repro repo if useful.
Activity
Fix 5 issues: .mjs import edges (Graphify-Labs#414), cache root path (G…
v0.4.20: fix #414 JS imports_from path normalisation, fix #418 graph.…
v0.4.20: fix Graphify-Labs#414 JS imports_from path normalisation, fix …