Modularity and Monorepositories
summary
Claims that a monorepo lets a team make atomic releases and share dev tooling across packages are demonstrated with concrete steps: initialize a repo with Lerna.js, run Lerna.js bootstrap simlinks to symlink packages, install Babel and webpack once at the root, and run Storybook for a living style guide. A demo with a header and button shows hot reloading across modules and real-time integration; the talk cites a ~30,000 lines of JavaScript monolith as motivation and notes real costs: slower git ops, tagging complexity, and added build-tooling decisions.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:37GOOD ARCHITECTURE COSTS LESS THAN BAD ARCHITECTURE
- 3:21WHAT DOES YOUR ORGANISATION LOOK LIKE?
- 4:01MONOLITH
- 5:31MONO A MONO A MONO
- 5:47$ npm run deploy
- 8:28SHARE COMMON FUNCTIONALITY BETWEEN PROJECTS
- 9:48MAKE ATOMIC CHANGES TO SHARED DEPENDENCIES
- 15:52LET'S ADD SOME CODE
- 20:58MAKE A CHANGE
- 21:46ONLY FOR FRONTEND?
- 26:06GIT CHECKOUT -- SLOWDOWN
- 26:49CREATIVE TAGGING
- 27:11BUILD TOOLING
related talks
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
05mJonathan Eskew - SeattleJS Conference
31mMonoRepos for the Masses
46mExploring the power of monorepos: When and why to use them
21mGit submodules: we have monorepo at home
20mBuilding with Monorepos
41mHandling Monorepos Today
19mKeynote: Why Monorepos