Repository navigation
Conversation
🌱 graft blast radiusNothing outside this diff depends on it. 1 area changed; no indexed dependents at depth 2. Who knows this code — 2 people across 1 area
Ownership is git history over each area's own files, weighted towards recent work (120-day half-life). Merge commits and bots are dropped, and you are dropped from your own PR. A name with no Test signal per changed area — 1 ✗Reached = a node under a test path has a resolved edge into the changed symbol. It undercounts anything called indirectly — through a CLI, a spawned process or a dynamic import — so read a low ratio as “look here”, never as a coverage gate.
Open the interactive graph → — click an area to see its dependent symbols at file:line. |
|
Thanks for this. #726 just merged and covers the same change: barrel re-exports now link in the graph, for plain JS barrels too, and generic supertypes as well. I checked your test case with the parser loading step added: it fails on main before #726 and passes with it. Your test as written also fails on current main because parsers now have to be loaded up front ( |
|
Thanks for checking. I compared the patch with #726: both add TypeScript re-export edges for barrel traversal, and I do not see a distinct case in this PR. I will close this as superseded. |
|
Superseded by #726, which adds the same TypeScript re-export traversal behavior. |
Track TypeScript re-export sources as import dependencies so reverse impact traversal reaches consumers through barrel files.
Added a local regression covering the re-export target, a downstream consumer, and its test file.
Validation: focused graph tests (54 passed), TypeScript check, and diff check passed.
npm testpassed 3,974 tests before hanging in the existing SSE watcher test; the full suite did not complete.Fixes #653