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
TypeScript: calls through a renamed named import (import { foo as bar }) produce no CALLS edge #2297
trace_path (inbound) misses callers that invoke a function through a renamed named import.
Plain named imports and namespace imports resolve correctly, so the gap is specific to the as alias.
src.renamed.callsRenamed listed as a caller too (3 callers).
Real-world impact
In a pnpm TypeScript monorepo (≈2.8k source files, index_mode full), 37 value imports in 19 files use import { X as Y } from "@scope/pkg". A common pattern is an app-local wrapper that binds an app-specific argument:
Thank you for the plain, namespace, and renamed import controls. They make the alias-specific missing caller clear without conflating it with re-export aliases. I have added the bug classification; the resolution still needs verification.
Thank you for the controlled import-alias example. The missing caller through the renamed import still needs maintainer verification. Sorry for the delay; I’ll follow up soon.
Activity
DeusData commentedon Oct 19, 2026
Thank you for the plain, namespace, and renamed import controls. They make the alias-specific missing caller clear without conflating it with re-export aliases. I have added the bug classification; the resolution still needs verification.
DeusData commentedon Oct 25, 2026
Thank you for the controlled import-alias example. The missing caller through the renamed import still needs maintainer verification. Sorry for the delay; I’ll follow up soon.