Yarn in Depth: Why & How
summary
Yarn claims to be a project manager not just a package manager and backs that with specifics: builds move from Webpack to ESBuild, the repo uses zero-installs (keeping caches inside git) so CI installs drop from minutes to seconds, the monorepo runs about 44 workspaces, and a constraints system auto-enforces and often auto-fixes dependency/version rules. Development runs TypeScript, CLI-driven integration tests, end-to-end checks against real projects every 4 hours, and a lightweight plugin model that ships features like telemetry and patching.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:43Core Values
- 2:40Soundness
- 3:11Good Practices
- 3:39Default Behaviors
- 6:36Zero Installs
- 9:44Telemetry Integration
- 15:06Testing Strategy
- 18:45Where Do We See Yarn in the Future
related talks
22mYarn — 2019 and Beyond
20mThe Zen of Yarn
22mThe Complete Yarn Workflow
51mYarn Berry: a next generation package manager
23mSeeing Your Place in a New Way: Utilizing Yarn Package Management in a React SPA Map Viewer
19mNpm, Yarn — What If the Truth Lies Elsewhere
27mnpm i g @next and beyond: Building the future of package management
25mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript Project