The 6.0 API was the compiler itself: require("typescript") loaded it into your process, so tools held ts.Node and ts.Type objects, patched the language service (tsserver plugins) and passed custom transformers to emit. The Go port cannot do that. The team's API issue (#63800) says: "we can't dynamically link third-party code into the server process."
- 7.0 ships no API. On 7.0.2 the
typescriptentry exports onlyversionandversionMajorMinor; experiments sit undertypescript/unstable/*. API tools keep 6.0 through an npm alias,"typescript": "npm:@typescript/typescript6", with 7.0 installed under another name for the CLI. - 7.1 (beta on 20 October 2026, RC planned about a month later) ships a new, different API:
typescript/sync,typescript/async,typescript/ast,typescript/fs. A JavaScript client spawns the native compiler and calls it over IPC. The API, programs and snapshots are disposable (using), and types and symbols are remote handles with lazy methods (type.getSymbol(), nottype.symbol). Much ofProgramandTypeCheckeris mirrored, but every call is a round trip.
Per tool:
- typescript-eslint (8.72.0, peer
typescript <6.1.0) stays on 6.0. A draft PR addsprojectService: { EXPERIMENTAL_backend: 'native' }, adapting the 7.1 API to the classic shapes; it measures up to ~1.5x slower on many files, blaming the synchronous round trips, until bulk APIs land. - Volar-based tooling (Vue, Astro, Svelte, MDX) moves to content mappers: a package listed in tsconfig's
contentMappersthat gives TypeScript a virtual TypeScript view of, say,.vuefiles, with mappings back. Editors use it;tscneeds--runExternalCode. - Language-service plugins have no in-process equivalent: rewrite one as a content mapper or as a separate server that queries TypeScript through the API.
- Custom transformers: 7.1.0-beta's
emit()takes none.