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
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