TypeScript 7.0 is the native port with 6.0's defaults; 6.0 was the bridge release that deprecated everything 7.0 removes. So the migration is mostly a 6.0 cleanup:
- Upgrade to 6.0 and remove
ignoreDeprecations. On 6.0.3 each deprecated option is TS5101/TS5107."ignoreDeprecations": "6.0"silences them, but 7.0.2 ignores that and reports TS5102/TS5108 ("has been removed"). - Replace what 7.0 removes (6.0 release notes):
target: es5,downlevelIteration→ ES2015+; use another tool for ES5.moduleResolution: node/classic→nodenextorbundler.module: amd/umd/system/none,outFile→ ESM plus a bundler.baseUrl→ fold it intopaths, which must then be relative ("./src/*", else TS5090 on 6.0.3 and 7.0.2).esModuleInterop/allowSyntheticDefaultImports/alwaysStrict: false→ delete; they're always on.- Syntax:
module Foo {}→namespace(TS1540),assert {}→with {}(TS2880).
- Set the new defaults explicitly where you relied on old ones:
types(now[]),rootDir(now the tsconfig folder),strict(nowtrue),module/target(nowesnext/es2025). - Compare outputs with
--stableTypeOrderingon 6.0. The 7.0 announcement says code that compiles cleanly on 6.0 with it, and withoutignoreDeprecations, should compile identically on 7.0. It's diagnostic only: the 6.0 notes warn of up to 25% slowdown. - Switch the CLI.
--checkers(default 4) sets type-checking workers per project and--builderssets concurrent project-reference builds; more of either costs memory.--singleThreadedturns parallelism off for constrained CI. - Keep 6.0 for API consumers. 7.0 has no stable JavaScript API, so tools built on it (typescript-eslint, language-service plugins) keep 6.0 through the npm alias
"typescript": "npm:@typescript/typescript6". The 7.1 API is new and different, so they need a port, not a switch back;tsserverplugins can't load into the Go server at all.
JavaScript projects also check tsc/CHANGES.md in the TypeScript repo: JSDoc support was rewritten and some old forms are gone.