Member-only story
🦋 Changesets is a game changer
In today’s coding landscape, monorepos are all the rage. They offer a centralized, streamlined approach to managing multiple packages within a single repository.
But here’s the kicker: we often want independent versioning for these packages. If we were to do this manually, it would be a real hassle. That’s where 🦋 Changesets come into play.
By offering a clear and efficient way to manage independent versioning for packages within a single repository, Changesets has become a crucial addition to the toolkit of many developers and organizations.
Let’s dive into the magic of this technology and see how they simplify the complex world of monorepo versioning.
Project Structure
Following is the project structure of our sample monorepo. This repository contains five packages, four of which are private and one that is public. The private packages are marked with "private": true in their package.json files, indicating that they're not meant to be published to npm.
├── apps
│ ├── docs (Private)
│ └── web (Private)
├── packages
│ ├── eslint-config-custom (Private)
│ ├── tsconfig (Private)
│ └── ui (Public)
