TypeScript enums have surprising gotchas that many experts avoid.
Unlike most TS features, enums generate runtime code and aren't erased during compilation. They can't be used as type constraints and cause bundle bloat.

TypeScript introduced private class fields before JavaScript did. Its initial private keyword was later replaced by JavaScript's standard # syntax for private fields.

Template literal types let you create powerful string manipulation at the type level:

You can make TypeScript's type system Turing complete with recursive conditional types.
This means the type system itself can compute any algorithm... though you probably shouldn't 😅

TypeScript has built-in utility types for manipulating other types, but many devs reinvent them.

Instead of writing your own, use these standard ones:

Use type guards to ensure type safety in render methods:

Make component refs type-safe:

Type React event handlers properly:

Use type extraction for component props to keep your code DRY:

Leverage React.FC when you need access to children, defaultProps and contextTypes types:

Use discriminated unions for component states:

Kick off with precise component prop typing: