tailwind-config-viewer VS changesets

One more nifty tool that can help developers and designers alike working on a project like this is tailwind-config-viewer. As stated on the repo's page:

For versioning we use changeset, but with fixed-packages. We have found that the user thinks updating and managing our dependencies much easier if they can just bump each package to the same version. (storybook, sanity follows this appoach). While it feels unintuitive that each package gets a major if just the CSS has breaking changes, the user don't really care. They just want to finish the chore of updating their dependencies fast, without having to understand the system that deeply. This also makes documenting the changes much easier!

Thanks for sharing this. Why should I choose that instead of Changesets that work like a charm?

https://github.com/changesets/changesets works well for generating changelogs.

I found a tool named Changesets for versioning and publishing monorepo in PNPM’s docs. After some study on its philosophy, I believe it’ll be a good fit for monorepos:

The CI/CD pipeline is based on GitHub Actions and Changesets

This can be a lot of work — particularly maintaining a useful changelog. Which is why I use Changesets, which — together with its great GitHub Action — does pretty much all of this work for me.

Even better, with the help of GitHub Actions and Changesets, you can automatically manage versioning and publish the UI library to NPM.

Was the CI to slow before? Have you ever considered using something like changesets?

Use a library to generate automatic changelogs every time your code is updated. Chakra UI used Changesets.