Why we stopped using Lerna for monorepos

• lerna

  162 35,352 8.9 TypeScript

  :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.

  

ℹ️ TL;DR Our project Logto used PNPM + Lerna for dependency and monorepo management.

• release-please

  46 4,125 8.6 TypeScript

  generate release PRs based on the conventionalcommits.org spec

  

We are using dlx since our changelog was generated by the rules of Conventional Commits. If you don't need it, do this:

• 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.

  

• changesets

  30 7,998 5.7 TypeScript

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

  

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:

• logto

  99 7,211 9.9 TypeScript

  🧑‍🚀 The better identity infrastructure for developers and the open-source alternative to Auth0.

  

Our lockfile size decreased dramatically after removing Lerna, which didn’t affect our daily development. Actually, it’s hard to tell the difference, and I’m happy we could achieve the same experience with much fewer dependencies.

Suggest a related project