Microsoft has released TypeScript 6.0.1 RC, which introduces configuration changes to ensure existing projects can continue compiling while preparing for the upcoming TypeScript 7.0. To install the release candidate, users can run `npm install -D typescript@rc` and make necessary adjustments in their `tsconfig`, such as setting "strict": false for previously tolerated sloppy code and specifying "module": "commonjs" for non-ESM targets. The update also deprecates certain flags and offers new features like the experimental `--stableTypeOrdering` flag, which aligns union ordering with future releases. Users are advised to monitor deprecation warnings and test their codebase early to catch any issues before the full release

TypeScript 6.0.1 RC released: How to Install it Without Breaking Your Build

Microsoft’s TypeScript 6.0.1 RC arrives with a handful of configuration shifts that let existing projects keep compiling while preparing for the upcoming native Go‑based compiler in TS 7.0. The RC is pulled into a project by running npm install -D typescript@rc, and then a few tsconfig tweaks—such as setting "strict": false if sloppy code was previously tolerated, "module": "commonjs" when ESM isn’t the target, or specifying "types": ["node"] to avoid phantom “cannot find name” errors—eliminate most of the new error wall. The compiler now warns that baseUrl and legacy module resolution flags are deprecated; removing baseUrl and prefixing paths entries restores old alias behaviour without extra config. Enabling the experimental --stableTypeOrdering flag makes union ordering match how TypeScript will order them in 7.0, helping with declaration file comparison and surfacing inference differences that may require explicit type arguments or annotations to fix.

TypeScript 6.0.1 RC released: How to Install it Without Breaking Your Build @ NT Compatible