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 “secure” to make use of TypeScript 7.0 to validate a construct, Rosenwasser stated, 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 stated. For context, there have been round 20,000 compiler take a look at instances, of which about 6,000 produce not less than one error in TypeScript 6.0. In all however 74 instances, TypeScript 7.0 additionally produces not less than one error. Builders can confidently use TypeScript 7.0 as we speak to type-check a undertaking for errors, Rosenwasser stated. Past single-pass/single-project kind checking, the command-line compiler additionally has reached main parity. Options similar to --incremental, undertaking reference assist, 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. An inventory of upcoming deprecations in TypeScript 6.0 could be seen within the concern tracker. For emit, --watch, and API capabilities, the JavaScript pipeline will not be fully full. Builders who don’t want JavaScript emit from TypeScript, operating tsgo for a construct will work nice, Rosenwasser stated. Additionally, TypeScript 7.0 (Corsa) is not going to assist the prevailing Strada API. The Corsa API continues to be a piece in progress.
With TypeScript 6.0, there is no such thing as a intention to supply a TypeScript 6.1 launch, though there could also be patch releases for TypeScript 6. “You may consider TypeScript 6.0 as a ‘bridge’ launch between the TypeScript 5.9 line and seven.0,” Rosenwasser stated. “6.0 will deprecate options to align with 7.0, and will probably be extremely appropriate when it comes to type-checking habits.” The intent is to make sure that TypeScript 6.0 and TypeScript 7.0 are as appropriate as potential.
