[quackware]

This might make sense for performing a "final" build or for very small libraries, but IMO not really for anything beyond that or for any sort of application level codebase. Some of the links in OPs post mention projects and not necessarily libraries, where the amount of code included can increase pretty quickly and tsc is just so so so much slower then using a tool like vite/esbuild/tsx/vitest or similar swc derivatives. I think relying on your IDE for type checking and linting while periodically performing a full typecheck via tsc in CI could be the sweet spot. Not to mention other features like hot reloading, auto re-running tests, etc that these bundlers and tools that utilize them expose for you.

At least for me I think maintaining a tight feedback loop between "make a change" => "verify it works" is important to not be distracted by another task. esbuild taking 100 or so ms while tsc taking 30+ seconds makes a world of difference for that.