React application as API
summary
Claim: a huge React app becomes a set of independent, single‑responsibility endpoints. Implements small molecule containers (entry point, data fetching, side‑effects) plus optional presenter, router and utils layers to compose multi‑step flows. Shares state with reducers and HOCs and uses hooks for step state. Signals completion via a resolver API that posts messages or redirects back to the consumer. Uses lazy bundle split so each flow loads only its code, producing reusable, pluggable features that scale.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:43Definition of API
- 4:23Problems to solve
- 7:13Data management
- 9:33State management
- 9:56State control
- 13:12Resolver API
- 16:28Fusion
- 18:02Bundle Split
- 19:26Plugins
- 21:45Plugin example
