The native port of the TypeScript compiler additionally has made important progress, with TypeScript 7.0 kind checking almost full. A frequent query is whether or not it’s “protected” to make use of TypeScript 7.0 to validate a construct, Rosenwasser mentioned, or in different phrases, does the TypeScript 7.0 compiler reliably discover the identical errors that TypeScript 5.9 does? The reply is sure, he mentioned. For context, there have been round 20,000 compiler check circumstances, of which about 6,000 produce at the least one error in TypeScript 6.0. In all however 74 circumstances, TypeScript 7.0 additionally produces at the least one error. Builders can confidently use TypeScript 7.0 right this moment to type-check a undertaking for errors, Rosenwasser mentioned. Past single-pass/single-project kind checking, the command-line compiler additionally has reached main parity. Options corresponding to --incremental, undertaking reference help, and --build mode are all ported over and dealing.
TypeScript 7.0 will take away behaviors and flags deliberate for deprecation in TypeScript 6.0. A listing of upcoming deprecations in TypeScript 6.0 may be seen within the situation tracker. For emit, --watch, and API capabilities, the JavaScript pipeline just isn’t fully full. Builders who don’t want JavaScript emit from TypeScript, working tsgo for a construct will work superb, Rosenwasser mentioned. Additionally, TypeScript 7.0 (Corsa) won’t help the present Strada API. The Corsa API remains to be a piece in progress.
With TypeScript 6.0, there isn’t any intention to provide a TypeScript 6.1 launch, though there could also be patch releases for TypeScript 6. “You’ll be able to consider TypeScript 6.0 as a ‘bridge’ launch between the TypeScript 5.9 line and seven.0,” Rosenwasser mentioned. “6.0 will deprecate options to align with 7.0, and might be extremely appropriate by way of type-checking habits.” The intent is to make sure that TypeScript 6.0 and TypeScript 7.0 are as appropriate as doable.
