lerna VS single-spa

Compare lerna vs single-spa and see what are their differences.


:dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository. (by lerna)
Our great sponsors
  • Amplication - open-source Node.js backend code generator
  • Appwrite - The open-source backend cloud platform
  • SurveyJS - A Non-Cloud Alternative to Google Forms that has it all.
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • Sonar - Write Clean JavaScript Code. Always.
  • Mergify - Updating dependencies is time-consuming.
lerna single-spa
159 44
34,936 12,612
0.5% 1.0%
9.2 6.6
4 days ago about 2 months ago
TypeScript JavaScript
MIT License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of lerna. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-06.
  • Nx 16.8 Release!!!
    5 projects | dev.to | 6 Sep 2023
    On Netlify's enterprise tier, approximately 46% of builds are monorepos, with the majority leveraging Nx and Lerna. Recognizing this trend, Netlify has focused on enhancing the setup and deployment experiences for monorepo projects. In particular they worked on an "automatic monorepo detection" feature. When you connect your project to GitHub, Netlify automatically detects if it's part of a monorepo, reads the relevant settings, and pre-configures your project. This eliminates the need for manual setup. This feature also extends to local development via the Netlify CLI.
  • Mocha/Chai with TypeScript (2023 update)
    3 projects | dev.to | 12 Aug 2023
  • Help with library implementation in a big webapp
    2 projects | /r/webdev | 26 Jun 2023
    This is the exact problem monorepos were born to solve. Not only will a monorepo let you share UI components, you'll be able to gradually add shared application logic as well (for instance, do all of your apps have their own logic for connecting to a database? you could roll that into a shared library with a monorepo). There are a lot of tools for accomplishing this in JS, but probably the most popular is lerna, which is built on top of NX (though lots of teams roll their own monorepo in nx without lerna, which IMO is a totally valid option).
  • How to Build and Publish Your First React NPM Package
    8 projects | dev.to | 9 Jun 2023
    To begin, you need to prepare your environment. A few ways to build a React package include tools like Bit, Storybook, Lerna, and TSDX. However, for this tutorial, you will use a zero-configuration bundler for tiny modules called Microbundle.
  • Utility for making sure that I'm using the right `@types/react`
    2 projects | /r/typescript | 5 Jun 2023
    If so, are you using a monorepo tool like Nx or Lerna? If not, start there and see if it solves your problem.
  • [AskJS] Is there a silver bullet for consuming Typescript libraries in a Monorepo?
    5 projects | /r/javascript | 9 May 2023
    I mean I don't know what your monorepo looks like, but for example infernojs (actually written with typescript) uses lerna, and lerna seems simpler than typescript references
  • Understanding npm Versioning
    3 projects | dev.to | 4 Apr 2023
    Tools for publishing, such as Lerna (when using the --conventional-commit flag), follow this convention when incrementing package versions and generating changelog files.
  • How to split an Angular app into micro-frontend apps
    5 projects | dev.to | 27 Mar 2023
    We could improve part of this by using something like Lerna. With the right configuration, Lerna can be really helpful.
  • Need help making sense of TRPC + express + React setup
    2 projects | /r/typescript | 27 Mar 2023
    It feels dirty to be adding express as a dependency to a react project, but I'm pretty sure TRPC requires all of client and server code to be in the same node.js project, since types are shared. I've read that you can use a tool like Lerna to share types between node projects, but it requires a build step, which would diminish the benefits of TRPC.
  • What's New With Lerna 6.5?
    4 projects | dev.to | 22 Feb 2023
    For more information, check out the PR


Posts with mentions or reviews of single-spa. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-23.
  • Use web components for what they’re good at
    8 projects | news.ycombinator.com | 23 Aug 2023
    I’ve actually done that “web components as the interoperability layer”!

    It was this old angular 1.8 app with new features being written in angular-hybrid-ized angular 8. Ripping out angular-hybrid and separating the angular 1.8 routes from the modern angular routes was difficult, but now they were totally separate.

    The only thing linking them together was an object with some RXJS streams in it for state, and a little in-house wrapper “app” who just loaded one component or another depending on the URL and a hash of routes for config. (I’d probably use SingleSPA [1] now. Same thing really.)

    We could deploy them separately since the build just ends up being another JS file somewhere that just gets included with a script tag at runtime. No version bumping! No big mega build!

    We started replacing the remaining “old” routes 1 by 1 with a “new” counter part. That was the easiest part, and went at a pace devs were comfortable with (fast enough) and business folk could tolerate. (modular enough to not HAVE to be done all at once)

    Last I checked, the angular 1.8 stuff is gone years ago. :)

    [1] https://single-spa.js.org/

  • Micro-frontend with Module Federations [Part 1] - Vite
    2 projects | dev.to | 14 Jun 2023
    Module Federation is not the unique solution, for example single-spa
  • Angular et micro front-end : conseils et à la recherche d'un bon tuto
    3 projects | /r/programmation | 25 May 2023
  • Building a Large Scale Micro-frontend Application.
    2 projects | dev.to | 3 Apr 2023
    Single-SPA and module federation are potent tools for building scalable micro-frontends. Single-spa provides a framework for building a modular front-end application. It allows lazy loading of micro-frontends, which helps improve the application's performance. In contrast, module federation enables communication and dependency sharing between different micro-frontends. It reduces code duplication, which can help with scaling an application.
  • How to split an Angular app into micro-frontend apps
    5 projects | dev.to | 27 Mar 2023
    Since micro-frontend allows us to develop applications individually, this also means you can use different frameworks and libraries together to develop each section of this application. Of course, this will have some advantages and disadvantages. If you are using different technologies to serve different parts of the application, it won't be so easy to move developers within teams. However, the door is open, and if you want to do something like that, you could use something like Single SPA, or some other, to help you organize and connect the different technologies into a larger application.
  • Micro frontends example
    2 projects | /r/Angular2 | 24 Feb 2023
    Using single-spa
  • Monolith to Module Federation at RazorpayX
    4 projects | dev.to | 18 Feb 2023
    There are numerous micro-frontend frameworks like Single SPA, Open Components, Mosaic, and so on The configuration for these tools can get complex and difficult to manage as we add more apps since they require configuration at each layer — routing, dependency management, and development. This would complicate our tooling and hence, would not work for us.
  • How we do engineering at epilot
    3 projects | dev.to | 22 Jan 2023
    Our web application consists of microfrontends written in React and Svelte orchestrated by the single-spa framework.
  • You Might Not Need Module Federation: Orchestrate your Microfrontends at Runtime with Import Maps
    8 projects | dev.to | 5 Jan 2023
    The lightweight Nest.js Import Map Resolver server has two main roles: store and update the importmap, but also handle the submission of JS assets. Single-spa has a similar solution available.
  • [Docker] [VITE] [React] Rutas en Containers separados.
    2 projects | /r/programacion | 15 Oct 2022

What are some alternatives?

When comparing lerna and single-spa you can also consider the following projects:

turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]

nx - Smart, Fast and Extensible Build System

Bit - A tool for composable software development.

qiankun - 📦 🚀 Blazing fast, simple and complete solution for micro frontends.

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

piral - Framework for next generation web apps using micro frontends. :rocket:

pnpm - Fast, disk space efficient package manager

FrintJS - Modular JavaScript framework for building scalable and reactive applications

webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

husky - Git hooks made easy 🐶 woof!

Next.js - The React Framework