Yarn Berry: a next generation package manager
summary
Yarn Berry (Yarn 2/3) rearchitects Yarn with a plugin system, better workspace support, yarn dlx and constraints (written in Prolog) and an encouraged install strategy called plug-and-play (PnP) that eliminates node_modules by serving files from a zipped cache. Example repo sizes drop (demo: node_modules 482 MB vs .yarn/cache 94 MB) and a project can support zero installs by committing the cache. Some tooling (React Native, Flow) still needs the node_modules linker; migration uses yarn set version berry.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:08Yarn 2 A next generation package manager
- 3:06Don't panic! Yarn Berry is 100% Opt-In
- 3:55Yarn Berry is enabled per-project
- 5:31What's new?
- 6:30yarn workspaces foreach
- 7:05Constraints
- 8:04What about performance?
- 10:09What is Plug and Play?
- 10:22Some Quick Node History
- 12:07How do we solve this problem?
- 13:26How does it work?
- 17:44Upgrading to Yarn 2 and PnP
- 18:26You can enable Yarn 2 per project
- 40:16Is Plug n Play right for you? Let's discuss!
- 42:30What makes Yarn different?
related talks
22mYarn — 2019 and Beyond
21mYarn in Depth: Why & How
05mRevisiting Node modules
57mZen and the Art of Package Management
27mnpm i g @next and beyond: Building the future of package management
19mNpm, Yarn — What If the Truth Lies Elsewhere
10mStreamlining npm modules and lock files Management
23mSeeing Your Place in a New Way: Utilizing Yarn Package Management in a React SPA Map Viewer