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

This page summarizes the projects mentioned and recommended in the original post on /r/javascript

Our great sponsors
  • Appwrite - The open-source backend cloud platform
  • SurveyJS - A Non-Cloud Alternative to Google Forms that has it all.
  • Amplication - open-source Node.js backend code generator
  • Mergify - Updating dependencies is time-consuming.
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • Sonar - Write Clean JavaScript Code. Always.
  • changesets

    🦋 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

    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.

  • Appwrite

    Appwrite - The open-source backend cloud platform. The open-source backend cloud platform for developing Web, Mobile, and Flutter applications. You can set up your backend faster with real-time APIs for authentication, databases, file storage, cloud functions, and much more!

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts