The native port of the TypeScript compiler additionally has made important progress, with TypeScript 7.0 sort checking practically full. A frequent query is whether or not it’s “secure” 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 instances, of which about 6,000 produce at the least one error in TypeScript 6.0. In all however 74 instances, TypeScript 7.0 additionally produces at the least one error. Builders can confidently use TypeScript 7.0 at present to type-check a venture for errors, Rosenwasser mentioned. Past single-pass/single-project sort checking, the command-line compiler additionally has reached main parity. Options similar to --incremental, venture 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 problem tracker. For emit, --watch, and API capabilities, the JavaScript pipeline will not be totally full. Builders who don’t want JavaScript emit from TypeScript, operating tsgo for a construct will work nice, Rosenwasser mentioned. Additionally, TypeScript 7.0 (Corsa) is not going to help the prevailing Strada API. The Corsa API continues to be a piece in progress.
With TypeScript 6.0, there isn’t any intention to supply a TypeScript 6.1 launch, though there could also be patch releases for TypeScript 6. “You possibly can 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 will likely be extremely suitable when it comes to type-checking conduct.” The intent is to make sure that TypeScript 6.0 and TypeScript 7.0 are as suitable as potential.
