[AskJS] Advice on how to manage breaking changes in the first versions of a UI Library

• changesets

  30 7,998 5.7 TypeScript

  🦋 A way to manage your versioning and changelogs with a focus on monorepos

  

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!

• marked

  60 31,845 9.5 JavaScript

  A markdown parser and compiler. Built for speed.

  

While changeset still lacks some features like a unified changelog for all the package, this can be handled with some scripts. Using for example marked one could set up some parsing to create a unified changelog for the whole system.

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

Suggest a related project