TypeScript 5.6 has officially entered the release candidate (RC) stage, marking the next step toward its stable release. This update brings refinements and reversions based on community feedback and further enhances TypeScript’s type system and developer experience. Among the notable changes, Microsoft has renamed several new types and reverted a previous modification related to how the TypeScript language service searches for tsconfig.json files. These adjustments build upon the improvements introduced in the beta version, which focused on stricter type checks and improved usability.
One of the significant reversions in the RC involves the tsconfig.json search behavior in the TypeScript language service. Previously, TypeScript 5.6 attempted to locate every possible project file named tsconfig.json, which sometimes resulted in an excessive number of referenced projects being opened. This behavior has now been reverted to prevent unintended issues, while Microsoft continues exploring ways to reintroduce a more refined version of this feature in TypeScript 5.7. This change ensures a more predictable and efficient project resolution process for developers working with complex project structures.
Additionally, several types introduced in the beta have undergone renaming to improve clarity and usability. The previously introduced BuiltinInterator type, which described values backed by Iterator.prototype, has been renamed to IteratorObject. This type now has a revised set of parameters and includes new subtypes such as ArrayIterator and MapIterator. These refinements provide better type safety and clearer distinctions between different iterator implementations in TypeScript.
The RC also introduces a new --stopOnBuildErrors flag for --build mode, which halts the build process if errors are detected in a project. Moreover, enhancements in editor functionality include direct support for commit characters and the ability to define exclude patterns for auto-imports, offering a more tailored and efficient development experience. These updates, along with the stricter nullish and truthy checks introduced in the beta, reinforce TypeScript’s commitment to improving code quality and catching potential issues earlier in the development cycle.