Scaling React.js Applications
summary
Claim: start projects with concrete conventions so large React apps stay maintainable. Recommends group files by feature and split UI into containers (state) and components (view); use Redux plus Redux Saga for decoupled async flows; isolate styles with CSS Modules + postcss auto-reset so components remain portable; use webpack code splitting and Immutable.js for cheap deep equality to bail out high in the tree and cut unnecessary re-renders.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:52ElementalUI
- 3:39Unidirectional Data Flow
- 7:07Containers and Components
- 8:02Group by feature instead
- 8:55Easy renaming and moving
- 9:37Work in a single folder
- 10:05Reusable components
- 10:25Styling??
- 11:18CSS Modules
- 14:19Component Isolation!
- 14:38Data Fetching??
- 15:32redux-saga
- 17:50Decoupled Components
- 19:37Webpack Code Splitting
related talks
52mBuilding Modern React Applications
24mA Beginner's Guide to Code Splitting Your React App
29mBuilding Large-Scale Web Apps
33mMaximising performance with React code-splitting techniques
25mBreaking Down Your Web App
57mBuilding Scalable, Maintainable Apps Using TypeScript and React
49mNavigating the React Solar System
15mReact Best Practices in 15 Slides