0
Challenge · 83Tooling & Quality
TypeScript with React
Languageused in ~80% of apps
Every serious React job in 2026 is a TypeScript job. Types turn the bugs you used to find in production — a misspelled prop, a number where a string belongs, calling .map on undefined — into red squiggles in your editor before the code ever runs. PropTypes were removed in React 19; TypeScript is the baseline.
Core idea. You describe the shape of your data — props, state, events, refs — and TypeScript checks every use against that shape at compile time, giving you autocomplete and catching mismatches before they reach the browser.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
NameField.jsxhover the underlined tokens
1function NameField(props) {
2 const [name, setName] = useState();
3 const onChange = (e) =>
4 setName(e.target.value);
5 return <input value={name} onChange={onChange} />;
6}
Everything is any. props.lable, e.taget, or setName(42) all compile fine — the mistake only shows up when a user hits it in production.
↑ play a little first, then dig in