Maintaining Your Company’s Open-Source Ecosystem
summary
Company maintains a set of SDKs for Node, Vue, Next and React, publishes them to npm and ships source alongside build artifacts so debugging in production is possible. Packages declare main/module/exports and use semantic versioning; devDependencies (e.g., Vite) never land in users' installs while peerDependencies ensure compatibility. A Vite plugin standardizes SDK builds. Maintenance runs on a roughly weekly or monthly cadence to update deps and fix bugs, RFCs guide breaking changes, and packages are deprecated or duplicated when retired.
AI-written summary · about
chapters (10)
- 0:00Open-source ecosystems intro
- 3:11What is a package ecosystem
- 5:37Reasons for own packages
- 9:09How npm packages work
- 13:59Key fields in package.json
- 17:08Managing dependencies
- 18:57Package maintenance challenges
- 20:40Regular maintenance tasks
- 21:43Evolving and retiring packages
- 22:47Q&A
related talks
19mConsuming Open-source: A maintainer's perspective
39mManaging an Open Source Project
30mHappy Developers, Healthy Modules - Together We Can Do This
37mNode.js Package Maintenance...
39mSOS: Sustainable Open Source
11mVite's Philosophy
28mThe Progressive Path to Open Source: Lessons from Anthony Fu's Journey
10mInterview with Laurie Voss