Open-source project
lerna/lerna avatar
lerna/lerna

Lerna 10: The Nx-Backed Monorepo Tool That Refuses to Die

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

36,029 stars2,265 forksTypeScriptMIT

At a glance

What is it?
Lerna, now stewarded by the Nx team, is a TypeScript build system for multi-package JavaScript repositories. Version 10.1.1 shipped in October 2026, and the tool's future is tied to Nx's distributed caching and task orchestration.
Who is it for?
Adopt Lerna 10 if you manage a JavaScript or TypeScript monorepo and want a command-line tool that integrates with Nx's caching and task graph without abandoning npm or yarn workspaces. Skip it if you need fine-grained control over publishing workflows or if you cannot tolerate a tool whose roadmap is set by a commercial entity (Nx).
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • lerna/lerna36,029 ★ · -21
Star history
Repository2026-08-182026-11-15
lerna/lerna36.1k36k

-21 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What Lerna Actually Solves Today

Lerna solves a narrow but painful problem: managing multiple JavaScript or TypeScript packages that live in one repository. Without such a tool, you either publish each package with its own script or hand-roll version coordination. Lerna gives you commands to run tasks across packages, version them consistently, and publish them to npm. The README calls it a "fast, modern build system," which is a shift from its original role as a pure publishing tool. The target user is a team that has outgrown a single package but does not want to adopt a full monorepo framework like Nx or Turborepo on its own. The core value is not task running per se; it is the coordination of versions and publishes across many packages.

The Nx Stewardship Change and What It Means

The README opens with a warning in bold: "this project changed stewardship to Nx." That is a significant fact. Lerna is no longer an independent project; it is now driven by the team behind Nx, a competing monorepo tool. The blog post linked in the README, titled "Lerna 5.1 New Website, New Guides, New Lerna Example Repo, Distributed Caching Support, and Speed," indicates that Lerna's future is tied to Nx's architecture. The core team listed in the README consists of Nx contributors: Victor Savkin, James Henry, Benjamin Cabanes, and Juri Strumpflohner. This means that when you adopt Lerna, you are implicitly adopting Nx's roadmap. The practical implication is that Lerna's features will likely lean toward Nx's caching and task graph. If you were hoping for a neutral tool that stays out of the Nx ecosystem, this stewardship change is a red flag. However, it also means the project has active maintainers with commercial backing, which is better than an abandoned tool.

How Lerna Works: Commands and Data Flow

Lerna operates through a command-line interface. The README links to a getting started guide and a features page, but the repository itself does not include a command list. What is clear from the description is that Lerna runs tasks across packages, versions them, and publishes them. The Nx integration adds a task graph and caching layer. The README mentions "distributed caching support," which means Lerna can cache build outputs and share them across machines, avoiding redundant work. If you have used Nx directly, this will feel familiar. If you have not, you will need to learn the Nx task model.

Getting Lerna Running: Commands and Configuration

The README does not include installation commands, but the standard approach is to install Lerna as a dev dependency in your repository root: npm install --save-dev lerna. You also need a package manager workspace configured, such as workspaces in package.json. The getting started guide at lerna.js.org/docs/getting-started is the authoritative source, but from the repository layout, you can infer that lerna.json is the central config. For a minimal setup, you would have a root package.json, a lerna.json, and at least two packages. The documentation claims interactive tutorials, so you can learn by doing. But do not expect a zero-config experience; you must understand your workspace structure.

The Real Limitations: When Lerna Is the Wrong Tool

Lerna has genuine limitations. Lerna's versioning model is either fixed or independent, and both have trade-offs. Fixed versioning forces all packages to share a version number, which simplifies coordination but causes unnecessary version bumps for unrelated packages. Independent versioning gives flexibility but increases the chance of version conflicts and requires more manual attention. Second, the Nx stewardship means that some features may be deprioritized in favor of Nx's own tooling. The README does not list any unsupported features, but the history of Lerna 5.1 shows a pivot toward Nx features. If you are on a strict publishing workflow with custom hooks, you may find Lerna's behavior opaque.

Alternatives: Nx, Turborepo, and Plain Workspaces

The most direct alternative is Nx itself. Nx offers a full task graph, caching, and distributed execution, and it is the same underlying technology that now powers Lerna. The difference is scope: Nx is a complete monorepo framework with plugins for many languages, while Lerna is a thinner layer that focuses on versioning and publishing. If you already use Nx, you do not need Lerna; Nx has its own version and publish commands. Another alternative is Turborepo, which is a build system that caches task outputs but does not handle versioning or publishing. You would pair Turborepo with changesets or semantic-release. The difference in approach is that Turborepo is a task runner only, leaving versioning to separate tools, while Lerna bundles versioning and publishing. A third alternative is to use your package manager's native workspaces, such as npm workspaces or pnpm workspaces, plus a simple script for publishing. That approach gives you full control but requires you to build your own versioning logic. Lerna's advantage is that you get a tested, opinionated workflow out of the box.

Maintenance and Upgrade Cost

The release history shows active maintenance: v10.0.1 on August 19, 2026, v10.1.0 on October 9, 2026 and v10.1.1 on October 12, 2026. The project is not archived, and the last push was on October 31, 2026, so the maintainers are actively committing. The license is MIT, which is permissive and imposes no restrictions on commercial use. However, the stewardship by Nx means that the project's direction is influenced by a commercial company, Nx. This is not a legal issue, but it is a governance concern. If Nx changes its strategy, Lerna could be deprecated or merged into Nx. The README's own link to the Nx blog suggests that Lerna's identity is already merging into Nx's. For upgrade cost, you should expect breaking changes between major versions. The jump from v9 to v10 likely includes changes to configuration or command behavior, but the README does not specify. You should read the changelog and test your lerna.json against v10 before upgrading. The cost is moderate: you need to retest your CI pipeline and publishing workflow.

Who Should Pick Lerna Over Nx or Turborepo

Lerna fits a specific niche: teams that want a command-line tool for versioning and publishing multiple packages without adopting a full monorepo framework. If you already have a working monorepo with npm workspaces and you only need to automate releases, Lerna is a reasonable choice. It is also a good entry point if you plan to migrate to Nx later. However, if you are starting a new monorepo and you know you will need advanced caching or remote execution, you should skip Lerna and go straight to Nx. If you only need task running and you are comfortable with a separate versioning tool, Turborepo plus changesets is a lighter alternative. The README does not provide benchmarks or user counts, so do not base your decision on popularity. Base it on the workflow you need. Lerna gives you a bundled versioning and publishing system, but it comes with the Nx dependency. That is the trade-off you must accept.

Editorial conclusion

Adopt Lerna 10 if you manage a JavaScript or TypeScript monorepo and want a command-line tool that integrates with Nx's caching and task graph without abandoning npm or yarn workspaces. Skip it if you need fine-grained control over publishing workflows or if you cannot tolerate a tool whose roadmap is set by a commercial entity (Nx). Before adopting, verify that your existing lerna.json configuration is compatible with v10, test the version and publish commands on a dry run, and confirm that the Nx integration does not force you into a different package manager. The project is alive, but its identity is now Nx's.

Frequently asked questions

How do I install Lerna?

The README carries no install command at all. It points to lerna.js.org and to a Getting Started page at lerna.js.org/docs/getting-started, and it links the package on npm, so both the install steps and the package location sit one hop from the landing page.

How do I install Lerna on macOS?

Nothing in the repository is specific to macOS or to any other platform. The closest thing to a platform requirement is the Volta block in the root manifest, which pins Node 26.12.0 and npm 12.2.0, and those pins are for building Lerna rather than for consuming the published package.

How do I use Lerna?

The README names no commands, so usage has to come from the Features page at lerna.js.org/docs/features and the guides linked from the same site. What the repository does show is the shape of a setup: three npm workspaces named packages/lerna, website and libs/e2e-utils, and a release script that builds the lerna package through Nx before running tools/scripts/lerna-release.mjs.

What is Lerna used for?

Managing and publishing several JavaScript or TypeScript packages out of one repository, which is the scope the project sets for itself. Configuration lives in lerna.json at the repository root, next to package.json, nx.json and tsconfig.base.json, rather than inside package.json.

What is lerna.json?

It is the configuration file at the repository root, and the README does not document a single key inside it. A team starting from this repository cannot derive a working config from the source alone, so the documentation site is the only starting point named.

What is Lerna AI?

Nothing in the README describes an AI feature, and the project's own description covers package management and publishing only. The root of the repository does carry AGENTS.md and CLAUDE.md, but the README links to neither, so what you find first is working instructions for the repository rather than a shipped capability.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/lerna-lerna.svg)](https://hysenlabs.com/projects/lerna-lerna)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/lerna-lerna.svg)](https://hysenlabs.com/projects/lerna-lerna)

Was this useful?