Versioning and Publishing to npm
Use semantic versioning, automate changelog generation with Changesets or standard-version, and publish the library to npm or a private registry.
Why Publish to npm?
If your design system is used by more than one app, publish it as a package. Consumers install with npm/yarn/pnpm, lock to versions, and update on their schedule.
Semantic Versioning (SemVer)
Versions follow MAJOR.MINOR.PATCH. MAJOR: breaking changes. MINOR: new features, backwards-compatible. PATCH: bug fixes only.
All lessons in this course
- Storybook: Stories Controls and Docs
- Design Tokens with Style Dictionary
- Versioning and Publishing to npm
- Consuming a Design System