fix(ts): a re-export imports its module, and sync follows barrels of barrels

[colbymchenry]

Problem

An export … from './x' statement left almost nothing in the graph. Both extractors emitted one imports reference per re-exported name (export { A } from './x' → A). They emitted nothing for the module itself, and nothing at all for export * from './x'. Two things followed:

• A barrel made only of export * lines had no dependency on what it re-exports. A module's dependents, and so codegraph affected, missed the barrel.
• Sync couldn't follow a barrel of barrels. fix(sync): imports through a re-exporting module follow it when it is deleted or added #2512 made sync re-open what the files importing a deleted or added module bind through it. It finds those importers by the module edge into the file, and an outer index.ts with export * from './dropdown-menu' has no such edge. So when the inner barrel was deleted, the outer barrel's importers kept edges resolved through it. When the inner barrel was added, they kept the edges a name lookup had made in its absence. A fresh index of the same tree disagreed. This was fix(sync): imports through a re-exporting module follow it when it is deleted or added #2512's residue "Nested ES-module barrels".

Fix

• A re-export imports its module, as import … from does, in both extractors:
  • src/extraction/tree-sitter.ts calls extractImport for an export_statement with a source.
  • codegraph-kernel/src/tsjs/mod.rs calls extract_import for one.
  • Each creates an import node named by the specifier and a module reference, which links the barrel to the file it names, as an import's module reference does. The per-name references stay as they were.
  • The import node also lets a bare or scoped specifier ('reka-ui', '@scope/pkg') pass the resolver's name pre-filter, as an import statement's does.
• Sync follows modules that re-export a changed one (src/resolution/module-importers.ts):
  • Through the new edges, level by level, carrying the names each passes on: export * passes everything, a named or renamed re-export its exported name, export * as ns the namespace.
  • Up to REEXPORT_MAX_DEPTH, as far as the resolver's findExportedSymbol chases a re-export.
  • An ES namespace import (import * as z from './index') reads whatever its module passes on. Python keeps fix(sync): imports through a re-exporting module follow it when it is deleted or added #2512's rules.
• The "parse produced no symbols" warning doesn't count a re-export's import node. A barrel with an unparseable line (export type * from, TypeScript 'export type * from' makes the whole file parse to no symbols #2474) still reports it, as status-index-health.test.ts pins.

Fresh indexes change for JavaScript and TypeScript files with export … from statements: one import node, its contains edge, and a module edge (or a failed reference) per statement. The CHANGELOG asks users to re-index.

Validation

Tests

• __tests__/extraction.test.ts:
  • a re-export creates the import node and module reference, for export *, a named re-export and export * as;
  • an export *-only barrel is a dependent of its module.
• __tests__/sync-module-importers.test.ts, ES-module fixture: an outer src/ui/index.ts (export * plus a renamed re-export), and kit.ts passing one name on, read through a namespace import. Deleted, restored and added late, each compared with a fresh index of the final tree in a second folder.
• On main, 4 of these fail.
• Each part has teeth, checked by mutation:
  • without the TS extractor's import: 4 tests fail (kernel off);
  • without the kernel's: 4 kernel parity tests and the 2 nested sync tests fail (kernel on);
  • without following ES re-exports: 2 fail;
  • without the namespace rule: 2 fail.
• They pass with the kernel on and off.
• Kernel parity (kernel-tsjs-parity, kernel-node-id-parity, kernel-grammar-parity) passes, including real-source parity on src/mcp/tools.ts.
• Full suite on Windows: 6,939 passed, 82 skipped. The one failure, git-index-currency (status.pendingChanges reports zero for a committed-but-unindexed file — the git fast path never hash-checks what git omits #1829, timing-based, run while the A/B loaded the machine), passed 13/13 twice in isolation.

Fresh-index A/B (main and this PR, kernel on). The only differences are the expected ones:

repo	import nodes	contains edges	module edges	failed module refs
vben	+679	+679	+625	+54
excalidraw	+171	+171	+155	+16
zod	+138	+138	+137	+1
vue3-element-admin	+38	+38	+37	+1

• Plus each file row's node count.
• No other node, edge or reference moved.
• takenote, requests, gin and serilog are byte-identical.
• The failed module refs are external packages (reka-ui, vue-i18n, zod) or workspace packages whose import statements fail the same way on main (@excalidraw/element: 414 failed import refs, none resolved).

Sync A/B. Each arm's synced graph is compared with its own fresh index of the same tree. Cells are differing graph lines, main → this PR. Barrels are every 2nd index.{ts,tsx,js,jsx}; the rest are every 7th source file.

repo	barrels deleted	every 7th deleted	barrels restored	every 7th restored	barrels added late	every 7th added late
zod	324 → 0	86 → 30	0 → 0	10 → 0	324 → 0	66 → 0
vben	560 → 560	279 → 273	0 → 0	100 → 96	478 → 478	220 → 210
excalidraw	5,399 → 5,399	3,693 → 3,693	44 → 44	24 → 24	5,438 → 5,438	3,502 → 3,502
vue3-element-admin	0 → 0	8 → 8	0 → 0	0 → 0	0 → 0	0 → 0
takenote	16 → 16	12 → 12	0 → 0	0 → 0	0 → 0	0 → 0

• In every scenario this PR adds no residue line that main doesn't have; it only removes them.
• Controls (requests in Python, gin in Go, serilog in C#; every 7th deleted, restored and added late): synced graphs byte-identical to main's in all 9 runs.

Cost. Sync wall time, main and this PR, two interleaved rounds:

scenario	main	this PR
zod, 9 barrels deleted	1.49 / 1.48 s	1.58 / 1.60 s
zod, 9 barrels added late	1.99 / 1.97 s	2.12 / 2.12 s
vben, 114 barrels deleted	3.04 / 3.06 s	3.17 / 3.13 s
excalidraw, 17 barrels deleted	2.36 / 2.36 s	2.42 / 2.40 s

Fresh-index time is unchanged within noise (vben 11.6 → 11.1 s, excalidraw 11.5 → 11.4 s, zod 8.3 → 8.2 s).

Residues

• Importers whose module reference never links to the file (excalidraw's whole residue, and vben's barrel ones). The statement's bindings resolve through the barrel, but its own module reference doesn't resolve to the file, so no edge leads sync from the barrel to them. The same is true on main for import statements, and for fix(sync): imports through a re-exporting module follow it when it is deleted or added #2512's single-level case. Two causes:
  • A bare scoped alias. import { debounce } from '@excalidraw/common' binds through tsconfig paths to packages/common/src/index.ts, but isJsPathSpecifier excludes bare scoped names, so all 381 such module refs fail (TypeScript/pnpm: workspace member imports fail when the entry is declared via package.json "main"/"exports" (e.g. ./src/index.ts) — a same-name private function then hides real callers #2502 is related).
  • A Vue, Svelte or Astro importer. isJsPathImportRef covers only JS_MODULE_LANGUAGES (JS, JSX, TS, TSX, ArkTS), so vben's dropdown-menu.vue importing '../../ui' fails, as do all 357 relative module refs from .vue files there.
• takenote's 16 and 12: the same on main (Express mount route names after router/index.ts is deleted, and NoteItem).

Overlap

• test(graph): pin an end-to-end graph baseline and deletion invariants #2518 (open): its golden snapshot's fixture entry point has three export … from lines, which now gain an import node, a contains edge and a module edge each. Whichever of the two lands second regenerates that golden.
• fix(ts): a type-only re-export through a barrel is followed #2483 and fix(resolution): honour TypeScript type modifiers on imports and re-exports #1955 (open) change the re-export reader for type-only re-exports. This PR reads extractReExports as it is, and only exports REEXPORT_MAX_DEPTH.
• Follows fix(sync): imports through a re-exporting module follow it when it is deleted or added #2512 (merged), whose residue this closes for relative specifiers.

🤖 Generated with Claude Code