Maintaining your company’s open-source ecosystem
summary
Defines a package ecosystem as all packages an entity owns and shows concrete practices: use scoped npm registries, publish packages with proper main module exports field mappings so CJS and ESM work, declare peer dependencies (Vue router → vue) and keep build tools as devDependencies. Describes a real Vite plugin that centralizes SDK build config across multiple Prismic SDKs, reports maintenance cadence of once a week if issues exist otherwise monthly, and recommends RFCs for major API changes.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:19Package Ecosystems
- 5:02What's a Package Ecosystem?
- 6:23Package Ecosystem Recap
- 19:58Have you ever opened an issue or a feature request on an open-source project?
- 22:04Maintaining Packages
related talks
37mNode.js Package Maintenance...
19mConsuming Open-source: A maintainer's perspective
10mInterview with Laurie Voss
28mThe Module Ecosystem - The Stress of Success - Michael Dawson and Dominykas Blyze
21mVue's Road to Vite
17mA developer's take on security
34mTowards a simpler JavaScript ecosystem
14mAnalog: Building an Ecosystem of Ecosystems with Vite