Lerna Config Migrator

Lerna was transferred from the original maintainer to Nx (Nrwl) in 2022 and is technically still maintained, but its core functionality is largely deprecated. `lerna bootstrap` (the main value proposition) is removed — you should use native package manager workspaces instead. `lerna run` is replaced by Turborepo or Nx's task runners with much better performance. `lerna version` and `lerna publish` still work but are being superseded by Changesets for versioning. Most teams migrating in 2024 move to Turborepo + Changesets or full Nx.

Choose Turborepo if: you want a minimal, fast task runner with low configuration overhead, your team already knows how task-level caching works, and you don't need code generators. Choose Nx if: you want a full development platform with generators ('create a new React component'), project graph visualization, built-in support for many frameworks (Angular, React, NestJS, Next.js), and you need the affected detection to be highly accurate based on a full project dependency graph. Nx scales better for very large monorepos (100+ packages).

`lerna bootstrap` with `--hoist` was Lerna's way of installing dependencies across all packages and hoisting shared deps to the root. Replace it with your package manager's built-in workspace install: `npm install`, `yarn install`, or `pnpm install` — all handle workspace package linking and hoisting natively. If you used `lerna bootstrap --ci`, use `npm ci` / `pnpm install --frozen-lockfile` instead. The package manager approach is faster and more reliable.

Use Changesets as the drop-in replacement. Install with `pnpm add -D @changesets/cli && pnpm changeset init`. Workflow: 1) `pnpm changeset` — developers add changeset files describing changes, 2) `pnpm changeset version` — replaces `lerna version`, bumps package.json versions and generates CHANGELOG.md, 3) `pnpm changeset publish` — replaces `lerna publish`, publishes changed packages to npm. For Nx users, use `nx release` which is Nx's built-in versioning and publishing pipeline.

If you used `lerna version --conventional-commits`, migrate to Changesets with `@changesets/changelog-github` for a similar PR-linked changelog. If you want to fully retain conventional commit automation, use `@changesets/cli` with `--snapshot` mode or configure `nx release` with `conventionalCommits: true`. Alternatively, use `semantic-release` with workspace plugins as a conventional-commit-native alternative to both Lerna and Changesets.

Both Turborepo+Changesets and Nx Release support independent versioning out of the box — each package gets its own version based on what actually changed. This is actually the default in Changesets (each changeset targets specific packages). Nx Release also supports independent mode. The key difference from Lerna's independent mode: you explicitly write changeset files describing what changed and at what semver level, rather than Lerna inferring from commit messages (which was often wrong).