manypkg

In version 0.8.0, a new check INTERNAL_DEV_DEP_NOT_STAR was introduced. This check ensures that devDependencies pointing to internal workspace packages use the * version range instead of a specific semver range.

Why use this? Internal dependencies are always linked in a monorepo. Using * prevents unnecessary package patches that would otherwise occur if an internal dependency's version moved outside a specific semver range, as the link remains valid regardless of the version.

// Before (with specific range)
{
  "name": "sunshine",
  "devDependencies": {
    "sun": "^1.0.0"
  }
}

// After manypkg fix
{
  "name": "sunshine",
  "devDependencies": {
    "sun": "*"
  }
}

To use Manypkg in your monorepo, install the @manypkg/cli package using your preferred package manager (the example uses Yarn):

yarn add @manypkg/cli

Install the @manypkg/find-root package using your preferred package manager to enable monorepo root detection.

yarn add @manypkg/find-root

You can configure Manypkg by adding a manypkg key to your root package.json file. Supported options include:

• defaultBranch: The correct name for your repository branch (used by the Incorrect repository field rule). Defaults to main.
• ignoredRules: An array of rule keys to disable. Defaults to [] (all rules enabled).
• workspaceProtocol: Determines if the workspace: protocol for internal packages is required or allowed. Defaults to allow.

{
  "name": "monorepo-root",
  "private": true,
  "manypkg": {
    "defaultBranch": "main",
    "ignoredRules": ["EXTERNAL_MISMATCH"],
    "workspaceProtocol": "allow"
  }
}

When using the run command, if you have packages with overlapping names (e.g., packages/pkg-a and packages/pkg-a-1), you can target the exact package by providing its exact directory name or its exact package name. This prevents the command from matching substrings of other packages.

# Target by exact directory name
yarn manypkg run packages/pkg-a

# Target by exact package name
yarn manypkg run @project/package-a

Use @manypkg/find-root to locate the root directory of a monorepo. It supports workspaces managed by Yarn, npm, Lerna, pnpm, Bun, or Rush.

• findRoot(startDir): An asynchronous function that returns a Promise resolving to the root directory path.
• findRootSync(startDir): A synchronous function that returns the root directory path directly.

Both functions require a starting directory (e.g., process.cwd()) as an argument.

import { findRoot, findRootSync } from "@manypkg/find-root";

// Asynchronous usage
let dir = await findRoot(process.cwd());

// Synchronous usage
let dir = findRootSync(process.cwd());

Use @manypkg/get-packages to programmatically discover packages within a monorepo. It automatically detects the monorepo manager being used (Yarn, npm, Lerna, pnpm, Bun, or Rush) and supports single-package repositories as well. The library uses @manypkg/find-root to locate the project root starting from the provided directory.

It provides two main functions:

• getPackages(directory): An asynchronous function that returns a promise.
• getPackagesSync(directory): A synchronous function for simpler execution flows.

import { getPackages, getPackagesSync } from "@manypkg/get-packages";

// Asynchronous usage
const { tool, packages, rootPackage, rootDir } = await getPackages(
  process.cwd()
);

// Synchronous usage
const { tool, packages, rootPackage, rootDir } = getPackagesSync(process.cwd());

You can enforce that all internal package dependencies use the workspace: protocol by setting the workspaceProtocol option in your manypkg configuration within the root package.json.

Configuration Key:

• workspaceProtocol: Set to `