Repository navigation
codebase-memory graph it doesn't resolve TypeScript aliases like @packages/shared #730
Description
Version
codebase-memory-mcp 0.8.1
Platform
macOS (Apple Silicon)
Install channel
GitHub release archive / install.sh / install.ps1
Binary variant
standard
What happened, and what did you expect?
The codebase-memory graph resolves imports by direct file path, but it doesn't resolve TypeScript aliases like @packages/shared → ../../packages/shared/src/index.ts. This generates a massive amount of fake dead code for everything imported via alias. I did the tests using codebase-memory-mcp from opencode
Reproduction
The codebase-memory graph resolves imports by direct file path, but it doesn't resolve TypeScript aliases like @packages/shared → ../../packages/shared/src/index.ts. This generates a massive amount of fake dead code for everything imported via alias. I did the tests using codebase-memory-mcp from opencode
Logs
Diagnostics trajectory (memory / performance / leak issues)
Project scale (if relevant)
No response
Confirmations
- I searched existing issues and this is not a duplicate.
- My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.
Reacted by Alexandros Pappas
Activity
DeusData commentedon Jul 1, 2026
Thanks. TypeScript path aliases/import maps need to resolve into the graph, otherwise alias-heavy repos will look like they have fake dead code. I’m tracking this under parsing/extraction quality. The smallest useful repro is a
tsconfigpathsalias plus one import through that alias, asserting the import resolves to the real target.sahil-mangla commentedon Jul 2, 2026
@DeusData Can i work on this task?
apappas1129 commentedon Jul 2, 2026
related #308
fix(pipeline): resolve ../ climbs in tsconfig path alias targets