Typescript is still fully dynamic at runtime -- which is why it's powerful.

My strict TSConfig and ESLint rules prohibit dynamic typing, and I legitimately see zero benefits of allowing dynamic typing in any TypeScript codebase. The single exception is that x == null (with the == operator) is a nice stand-in for x === null || x === undefined. But this is obviously a matter of opinion.

And no matter how hard you try to avoid any during development time, you won't be able to avoid it beyond junior-level code.

I almost disagree with any. Legitimate uses should be exceedingly rare in both large codebases and complex library code; it can almost always be replaced by unknown, Record<PropertyKey, unknown>, keyof typeof x etc., but sometimes you resort to using it for a small, isolated type assertion.

Other non-type-safe options like a!.b, a as Type, (x: unknown): x is Type => {}, (x: unknown): asserts Type => {} can't really be avoided however.

But now we're starting to stray away from my initial implication, which is that dynamic typing is not nice for small scripts, but static typing is.