Course contentsShow
← TypeScript
Lesson 1194 of 1,79628. tsconfig in DepthFree lesson

Future Additions to strict

How the strict flag evolves as new type-safety features are added to TypeScript.

Future Additions to strict

What you'll learn: How TypeScript's strict flag evolves over time to include new type-safety features.


The Living Nature of strict

The strict compiler flag isn't a fixed set of rules—it's a growing collection of type-safety checks that expands with each TypeScript release. When the TypeScript team introduces new strictness options that catch common errors, they eventually get bundled under the strict umbrella.

Think of strict like a "safety subscription service." When you enable it, you're opting into not just today's best practices, but also future improvements. It's TypeScript's way of saying: "give me the strongest guarantees available, now and in the future."

How New Flags Join strict

When TypeScript adds a new strictness flag, it follows this pattern:

  1. Introduced as standalone option - The new flag appears first as its own tsconfig.json setting (like useUnknownInCatchVariables once was)
  2. Separate adoption period - Teams can test it independently without enabling all of strict
  3. Promoted to strict - In a later major version, it becomes part of the strict family

This means if you have strict: true, you automatically get new strictness checks when you upgrade TypeScript—no configuration change needed.

Why This Matters

For existing projects, this can be a breaking change. Code that compiled with TypeScript 4.x might show new errors under TypeScript 5.x if strict is enabled, because new checks were added.

For new projects, it's a gift: you always get the latest safety features without manually tracking what's new.

Key Takeaway: The strict flag is forward-looking—enabling it means accepting stronger type safety as TypeScript evolves, which helps catch bugs early but may require code updates during TypeScript upgrades.