"The native port of the TypeScript compiler also has made significant progress, with TypeScript 7.0 type checking nearly complete. A frequent question is whether it is "safe" to use TypeScript 7.0 to validate a build, Rosenwasser said, or in other words, does the TypeScript 7.0 compiler reliably find the same errors that TypeScript 5.9 does? The answer is yes, he said. For context, there have been around 20,000 compiler test cases, of which about 6,000 produce at least one error in TypeScript 6.0. In all but 74 cases, TypeScript 7.0 also produces at least one error."
"Developers can confidently use TypeScript 7.0 today to type-check a project for errors, Rosenwasser said. Beyond single-pass/single-project type checking, the command-line compiler also has reached major parity. Features such as --incremental, project reference support, and --build mode are all ported over and working. TypeScript 7.0 will remove behaviors and flags planned for deprecation in TypeScript 6.0. A list of upcoming deprecations in TypeScript 6.0 can be seen in the issue tracker."
TypeScript 7.0 type checking is nearly complete and shows high parity with prior releases, catching almost all errors observed in extensive compiler tests. Approximately 20,000 compiler test cases exist, with about 6,000 producing at least one error in TypeScript 6.0; in all but 74 of those cases TypeScript 7.0 also reports an error. The command-line compiler reaches major parity with features like --incremental, project references, and --build mode ported and working. TypeScript 7.0 will remove behaviors and flags deprecated in TypeScript 6.0. JavaScript emit, --watch, and some API capabilities remain incomplete; tsgo can be used when JavaScript emit is unnecessary. The Corsa API will replace the Strada API but remains a work in progress. TypeScript 6.0 will act as a bridge release with possible patch updates but no 6.1 planned.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]