v1.4.0

[github-actions[bot]]

codeanalyzer-typescript v1.4.0

One theme: the Neo4j graph now carries everything analysis.json already knew about imports, exports, parameters and unresolved config reads. Three python-sdk accessors that refused on a TypeScript graph — get_imports, get_exports, get_method_parameters — can answer, and get_config_readers gets its unresolved counterpart. No breaking changes; the Neo4j contract stays 2.0.0 (every addition is optional-with-absent, so a 1.3.0 graph differs only by missing rows).

Highlights

Import and export bindings in the graph (#183, closes #182)

• TS_IMPORTS — one relationship per (importing module, target), every binding of that pair folded into spellings[], imported_names[], aliases[] and the TypeScript-only type_only_names[], so a runtime dependency graph can drop import type edges in one predicate. A resolved specifier lands on the real :TSModule; an external one on the same @external/<package root> ghost TS_PROVIDES / TS_UNRESOLVED_IMPORT already address (builtins under their own spelling, @external/node:fs). Python's aggregation rule and vocabulary.
• TS_RE_EXPORTS — the same shape for export … from, so barrel chains (index.ts re-exporting a tree) are walkable in Cypher. exports_json on :TSModule is the verbatim export list, including export { x as y } locals that are no edge.
• resolved_module on every import and re-export in analysis.json: the compiler's own answer (ts.resolveModuleName — tsconfig paths, directory index, .js → .ts), absent for externals and builtins. It is re-stamped every run, cached modules included, because the tsconfig and which files exist are state the content-hash cache cannot see.

parameters_json on :TSCallable — the parameter list verbatim (name, @formal_in:N id, type, default, optional/rest/readonly, accessibility, decorators, span), python's encoding, absent when empty. Measured at 1.4 % of graph.cypher on this repository. The SDK's TypeScript reconstruct already decodes it.

TS_READS_CONFIG_UNRESOLVED — :TSApplication → :TSExternal | :TSCallable, mirroring python's PY_READS_CONFIG_UNRESOLVED: a recognized config read that closed on no declared key, with key, reason (non-literal | undefined-key), prov[], keyed key|reason. Several sites collapse onto one edge (python's documented ceiling), so the graph count is a floor on the JSON list's. This release corrects the earlier claim that TypeScript emitted DEFINES_CONFIG alone — TS_USES_CONFIG was already there; only this counterpart was missing.

Also: export { type X } per-specifier type-only flags are now honoured in exports[] (they were dropped before).

Consumer queries for all of the above are in the shipped skill analyzing-cants-graphs (§1 structure, §7 config bridge). Design record: docs/design/specs/neo4j-bindings-parameters-config.md.

Known ceiling

The incremental Bolt push writes a module's edges only when that module changed. A binding edge's presence depends on the target existing, so an edge that flips absent → present while the importer is byte-identical (a target file added, a shard widened) waits for the importer to change or for --eager. Same class as TS_CALLS; removal is handled.

Upgrade

pip install -U "codeanalyzer-typescript==1.4.0"

brew upgrade codellm-devkit/homebrew-tap/codeanalyzer-typescript

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/codellm-devkit/codeanalyzer-typescript/releases/latest/download/cants-installer.sh | sh

A warm .codeanalyzer cache from 1.3.0 is invalidated automatically.

Links

• Release v1.4.0 — prebuilt binaries, wheels and the Neo4j schema contract
• Full diff, v1.3.0...v1.4.0