What

Index <JSXComponent /> tags as call-sites so component usage shows up in the code graph.
Resolve TS/TSX import paths (aliases from tsconfig.json and relative imports) to absolute file paths so two files importing the same module share one Module node instead of creating duplicates.

Why

Without this:

• <Layout> or <Button /> in .tsx files are invisible to the graph — no CALLS edge is created.
• import { capitalize } from "@utils/string-helpers" and import { capitalize } from "./utils/string-helpers" produce two separate Module nodes for the same file, fragmenting the graph.

How

JSX call-site indexing

• Added TypescriptJSXTreeSitterParser (extends the TS parser) with a _find_calls override that runs a tree-sitter query for jsx_opening_element / jsx_self_closing_element.
• PascalCase names are treated as component references; lowercase (<div>) is ignored.
• .tsx files now use the new typescriptjsx parser instead of reusing typescript.

TS import resolution

• New ts_import_resolver.py module with:
  • parse_tsconfig_paths(project_root) — reads tsconfig.json (handles // comments, trailing commas, one level of extends), returns baseUrl + paths map.
  • resolve_ts_import(specifier, importing_file, ...) — resolves in order: relative → alias → baseUrl → bare (returns None for npm packages).
  • _try_resolve_file(base) — tries exact path → .ts/.tsx/.js/.jsx → index.{ts,tsx,js,jsx}.
• graph_builder.py calls parse_tsconfig_paths once per indexing run, then passes the config to add_file_to_graph where each import is resolved before MERGE (m:Module {name: $resolved_path}).
• Module nodes now also store raw_specifier (the original import string) for debugging.

Example

// tsconfig.json: { "paths": { "@utils/*": ["src/utils/*"] } }

// src/App.tsx
import { capitalize } from "@utils/string-helpers";  // → resolves to /abs/src/utils/string-helpers.ts
import Layout from "./Layout";                        // → resolves to /abs/src/Layout.tsx

const App = () => (
  <Layout>              // ← CALLS edge to Layout component
    <Button />          // ← CALLS edge to Button component
  </Layout>
);

Testing

• Unit tests (test_ts_import_resolver.py, 25 tests): _try_resolve_file, relative imports, bare specifiers, alias imports, tsconfig.json parsing (comments, trailing commas, extends).
• Integration tests (test_ts_import_resolver_integration.py, 14 tests): parse the real fixture app-service.ts with tree-sitter, then resolve every import against the fixture's tsconfig.json.
• E2E tests (test_ts_indexing.py): index the full TS fixture into the DB and verify via Cypher that alias imports resolve to absolute paths, bare specifiers stay raw, JSX component calls are detected, and no duplicate Module nodes exist.
• Fixture: expanded sample_project_typescript with tsconfig.json paths, .tsx components (App.tsx, Layout.tsx, Button.tsx), alias-imported modules (string-helpers, math-helpers, user-model, constants, logger), and app-service.ts exercising all import patterns.