<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tsconfig on Tokenise</title><link>https://tokenise.rosvetic.com/tags/tsconfig/</link><description>Recent content in Tsconfig on Tokenise</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sat, 31 Oct 2026 11:07:00 +0000</lastBuildDate><atom:link href="https://tokenise.rosvetic.com/tags/tsconfig/index.xml" rel="self" type="application/rss+xml"/><item><title>Move to TypeScript 7 in two passes: get clean on 6.0, then diff the two compilers</title><link>https://tokenise.rosvetic.com/posts/typescript-7-migration-two-compilers-diff/</link><pubDate>Sat, 31 Oct 2026 11:07:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/typescript-7-migration-two-compilers-diff/</guid><description>&lt;p&gt;A project that compiles cleanly on TypeScript 6.0 can still fail on 7.0, and the reason is almost always one line in &lt;code&gt;tsconfig.json&lt;/code&gt;. 7.0 turned the options 6.0 deprecated into hard errors, changed what &lt;code&gt;rootDir&lt;/code&gt; and &lt;code&gt;types&lt;/code&gt; default to, and shipped without a programmatic API. None of that is hard to fix. The risk is finding it one CI failure at a time, or handing the whole thing to an agent that &amp;ldquo;fixes&amp;rdquo; errors by loosening the config.&lt;/p&gt;</description></item></channel></rss>