@lerna/add

@lerna/add

Add a dependency to matched packages

Install lerna for access to the lerna CLI.

Usage

$ lerna add <package>[@version] [--dev] [--exact] [--peer]

Add local or remote package as dependency to packages in the current Lerna repo. Note that only a single package can be added at a time compared to yarn add or npm install.

When run, this command will:

1. Add package to each applicable package. Applicable are packages that are not package and are in scope
2. Bootstrap packages with changes to their manifest file (package.json)

If no version specifier is provided, it defaults to the latest dist-tag, just like npm install.

Options

lerna add accepts all filter flags.

--dev

Add the new package to devDependencies instead of dependencies.

--exact

$ lerna add --exact

Add the new package with an exact version (e.g., 1.0.1) rather than the default ^ semver range (e.g., ^1.0.1).

--peer

Add the new package to peerDependencies instead of dependencies.

--registry <url>

Use a custom registry to install the targeted package.

--no-bootstrap

Skip the chained lerna bootstrap.

Examples

# Adds the module-1 package to the packages in the 'prefix-' prefixed folders
lerna add module-1 packages/prefix-*

# Install module-1 to module-2
lerna add module-1 --scope=module-2

# Install module-1 to module-2 in devDependencies
lerna add module-1 --scope=module-2 --dev

# Install module-1 to module-2 in peerDependencies
lerna add module-1 --scope=module-2 --peer

# Install module-1 in all modules except module-1
lerna add module-1

# Install babel-core in all modules
lerna add babel-core

Changelog

5.0.0 (2022-05-24)

Lerna workspaces no longer have dependency deprecation warnings.

Bug Fixes

• replace read-package-tree with @npmcli/arborist (#3133) (f1c10a4)
• resolve most dependency audit issues (#3127) (2b3b191)

BREAKING CHANGES

• Node v10.x and v12.x are no longer supported.

  • Please upgrade to the latest LTS release of Node (we recommend either v14 or v16).

• Internally npm lifecycle scripts are now invoked using @npmcli/run-script instead of npm-lifecycle in order to modernize the package and fix package vulnerabilities and deprecations.

  • We are classing this as a breaking change because the APIs of npm-lifecycle and @npmcli/run-script are significantly different, despite @npmcli/run-script being the official successor to npm-lifecycle.

    We have successfully made the integration test suite we inherited pass with this change, but there may potentially be aspects related to it which are not covered by the tests and are breaking. If you encounter any issues you believe are related to this change please open a new issue with a dedicated reproduction for us to look into!