TSCC
A native TypeScript compiler project focused on parsing, checking and compiling real TypeScript programs.
A native compiler project measured against real TypeScript behaviour.
TSCC implements the major stages of a TypeScript-oriented compiler pipeline in native code: parsing, binding and scope analysis, type checking, project/configuration behaviour and emission. The objective is not to call a parser “a compiler” and stop there.
Development is evidence-driven. Deterministic regression suites, oracle comparisons, sanitizer runs, TSX/CommonJS gates and representative project trials are used to identify which gaps actually prevent useful programs from compiling.
That approach keeps claims honest. Unsupported language areas stay visible until the evidence says they work, and new implementation checkpoints can be chosen from real project failures rather than the size of a feature checklist.
Useful capability without mandatory complexity.
The project stays focused on its own job; the surrounding Gantry tools remain optional.
Build a useful syntax tree and deterministic diagnostics across the implemented TypeScript surface.
Track scopes, symbols and type relationships rather than limiting the project to syntax translation.
Exercise configuration, module resolution, TSX and CommonJS behaviour in project-level gates.
Produce executable output for the supported language surface and test it against runtime expectations.
Start with the shortest path.
Advanced deployment or integration features appear only when the workflow actually needs them.
- 01
Compile focused samples and regression cases while developing a language slice.
- 02
Run representative project gates so parser/checker success is not confused with an application actually compiling.
- 03
Compare behaviour against pinned external oracles where that provides meaningful evidence.
- 04
Use the failure distribution to choose the next vertical slice instead of implementing features in arbitrary order.
Connections that remove real hand-off friction.
Each product already owns one side of these workflows. The integration exists to remove duplicate navigation, setup or context.
JS++
TSCC and JS++ occupy complementary compiler/runtime territory. TSCC can emit JavaScript-oriented output while JS++ explores embedding JavaScript execution in a native host; their tests can expose different sides of the same language/runtime boundary without requiring either project to depend on the other.
Explore JS++ →Cortex
Compiler development produces large, repetitive evidence loops—tests, diagnostics, project trials and mutation failures—that are well suited to Cortex-assisted investigation while the compiler itself stays an ordinary native project.
Explore Cortex →Warden
Warden can host the repository, terminals and long-running test workflows for TSCC when the compiler is being developed remotely.
Explore Warden →Local tool, no my.* indirection.
TSCC is primarily a CLI or embeddable native tool rather than a persistent web service. A my.* instance registry would add a choice where there is no running instance to choose.
It still belongs to Gantry Tools, appears in the project directory and can be exposed from a configurable my.gantry.cv launcher if somebody wants quick access to its website or documentation.
Why my.* is reserved for running applications →Where TSCC earns its place.
Implement TypeScript semantics in native code with a reproducible evidence trail.
Measure which real-world patterns are still blocking practical use.
Explore a TypeScript compiler that fits naturally beside other C/C++ tooling.
Explore TSCC.
Project-specific installation, commands and release details live on the project site.