Subito’s journey to a scalable monorepo
summary
Subito moves from injected runtime widgets to server‑rendered Next.js and a monorepo, using Lerna and conventional commits to automate version bumps, Jest test sharding and moduleNameMapper to run tests in parallel, and TurboRepo with an S3 remote cache to fetch build artifacts. Build times drop from over 20 minutes to about 1 minute, CI duration falls ~75%, and remote caching saves over a thousand developer hours since rollout.
AI-written summary · about
chapters (14)
- 0:00Subito’s monorepo journey
- 2:09Slow builds and legacy pain
- 5:18Runtime React injection
- 8:07Server-side rendering with Next.js
- 11:15Monorepo golden path
- 13:21Visibility and standardization
- 14:46Automating releases
- 16:33Growing build times
- 18:18Parallel CI pipelines
- 21:10Sharding tests
- 23:00TurboRepo caching
- 26:33Current pain points
- 28:19Why monorepos matter
- 29:45DevX improvements & Q&A
related talks
41mHandling Monorepos Today
29mModularity and Monorepositories
46mExploring the power of monorepos: When and why to use them
21mGit submodules: we have monorepo at home
01h 00mUsing Monorepos for Scalable Apps
29mFrom Monolithic Web App to Micro-Frontends – Extending Microservices Architecture to the Frontend
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
01h 03mMonorepo – How to do frontend faster, better and safer
