zeekay ef3d627de4 extract: <T> only where @hanzo/i18n/react binds it ...

0.5.0 read every JSX element named T. hanzo.ai's analytics page draws
its code sample with a local syntax-token <T k="key">import</T>, so a
scan of the wrapped tree added 23 keys: import, {, analytics.track(…

A file's T is now the name its import of @hanzo/i18n/react gives the
export: <T> from import { T }, <Say> from import { T as Say },
<i18n.T> from import * as i18n. A T the file defines, imports from
elsewhere, or imports as a type is not read. Over i18n-paths-ab the
scan drops exactly those 23 keys and nothing else (2094 -> 2071).

2026-10-22 18:45:55 -07:00

..

cli.ts

unreadable is not absent, in the two tools that write

2026-08-17 12:55:32 -07:00

english.ts

t takes elements and isolates arguments; English keys are extracted

2026-10-22 13:50:15 -07:00

jsx.ts

extract: <T> only where @hanzo/i18n/react binds it

2026-10-22 18:45:55 -07:00

scan.ts

finish the review: batching, and the guards each claim was missing

2026-08-17 14:24:34 -07:00