Introducing and Implementing React at Coolblue
summary
Coolblue adopts React to rebuild filter-heavy category UIs, hiring ~10 developers a month and needing fast iteration and refactorability; the stack locks on Redux for state, uses webpack with hot module replacement, isolates common build plumbing into an internal framework so teams write components without boilerplate, and enforces CI with unit tests (Karma + PhantomJS proves slow) so the move to Ava and Enzyme speeds tests. Dependency stability relies on npm shrinkwrap, and overall the approach works while exposing onboarding and ecosystem volatility as real costs.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:36Faceted Navigation
- 8:18Brands using React
- 10:59JavaScript fatigue
- 14:21Learning curve
- 18:08Integration
- 19:47Semantic Versioning
related talks
26mFrontend At Scale - Experiences Using React In A Large Organization
31mReact on Rails
34mI Heard React Was Good
19mPivoting to React, at scale
42mIntegrating React Into Legacy Projects
27mBuilding High Performance React Applications
28mBack to React: The Story of Two Apps
21mMigrating critical apps to React