React: The Most Common Mistakes in 2023
summary
Recommends switching foundations: use Vite over Create React App or consider Next.js for server rendering, move related code into a monorepo, and adopt TypeScript + Zod + MSW for safety and reliable local mocks. Cites that ~95% of teams now use TypeScript and a 3,000‑person poll where only ~5% often use useReducer. Advises unifying related state into one object, derive computed state instead of syncing in useEffect, prefer react‑query/SWR or server components for fetching, and memoize only when real cost appears.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:17Foundation
- 5:29Monor Repo
- 6:57TypeScript
- 12:08TypeScript ES Lint
- 13:14Lying to TypeScript
- 14:25Exporting Default on a separate line
- 18:50Overlooking Reuse Opportunities
- 19:57Design Systems
- 21:13Repeating Map Calls
- 23:58My Business
- 24:40State
- 27:27Multiple State Calls
- 30:13Use Effect
- 32:38Handling Forms
- 36:45Fetching
- 39:50QA
related talks
28mThe State of React State in 2019
37mReact & Next.js in 2025- Modern Best Practices for Faster, Smarter Apps
49mPicking a React Framework
38mState of React
01h 00mEffective React: Lessons from 10 Years
29mAvoiding the Biggest Mistakes in React State Management
17mManaging React State: 10 Years of Lessons Learned
34mState of the React Ecosystem