@lerna-lite/exec

(lerna exec) - Exec command [optional] 👷

Optional package extracted from Lerna exec command that will give us the ability to execute an arbitrary command in each package.

This package was added mainly because NPM Workspaces don't yet support executing commands in parallel and in topological order (they do have this RFC, so perhaps someday this package would become irrelevant :)).

---

Installation

``sh
npm install @lerna-lite/exec -D

then use it (see usage below)

lerna exec

or via pnpm

pnpm exec lerna exec
`

Usage

`sh
$ lerna exec -- [..args] # runs the command in all packages
$ lerna exec -- rm -rf ./node_modules
$ lerna exec -- protractor conf.js
`

Run an arbitrary command in each package.
A double-dash (--) is necessary to pass dashed flags to the spawned command, but is not necessary when all the arguments are positional.

The name of the current package is available through the environment variable LERNA_PACKAGE_NAME:

`sh
$ lerna exec -- npm view \$LERNA_PACKAGE_NAME
`

You may also run a script located in the root dir, in a complicated dir structure through the environment variable LERNA_ROOT_PATH:

`sh
$ lerna exec -- node \$LERNA_ROOT_PATH/scripts/some-script.js
`

Options

lerna exec accepts all filter flags.

`sh
$ lerna exec --scope my-component -- ls -la
`

> Note When executing the command in the shell, you will need to surround the command provided to lerna exec in quotes (what comes after double-dash -- ). Without this, the entire line is interpreted by your shell before lerna ever sees it and causes command flags to be returned as unknown. For example lerna exec -- 'git log -p -2'. This is not required when used as an npm script.

- @lerna/exec
- Usage
- Options
- --dry-run
- --stream
- --parallel
- --no-bail
- --no-prefix
- --profile
- --profile-location

> The commands are spawned in parallel, using the concurrency given (except with --parallel).
> The output is piped through, so not deterministic.
> If you want to run the command in one package after another, use it like this:

`sh
$ lerna exec --concurrency 1 -- ls -la
`

$3

Displays the execution command that would be performed without actually executing it. This could be helpful for troubleshooting.

`sh
$ lerna exec echo hello world --dry-run
`

$3

Stream output from child processes immediately, prefixed with the originating
package name. This allows output from different packages to be interleaved.

`sh
$ lerna exec --stream -- babel src -d lib
`

$3

Similar to --stream, but completely disregards concurrency and topological sorting, running a given command or script immediately in all matching packages with prefixed streaming output. This is the preferred flag for long-running processes such as babel src -d lib -w run over many packages.

`sh
$ lerna exec --parallel -- babel src -d lib -w
`

> Note: It is advised to constrain the scope of this command when using
> the --parallel flag, as spawning dozens of subprocesses may be
> harmful to your shell's equanimity (or maximum file descriptor limit,
> for example). YMMV

$3

`sh


Run a command, ignoring non-zero (error) exit codes


$ lerna exec --no-bail
`

By default, lerna exec will exit with an error if _any_ execution returns a non-zero exit code.
Pass --no-bail to disable this behavior, executing in _all_ packages regardless of exit code.

$3

Disable package name prefixing when output is streaming (--stream _or_ --parallel).
This option can be useful when piping results to other processes, such as editor plugins.

$3

Profiles the command executions and produces a performance profile which can be analyzed using DevTools in a
Chromium-based browser (direct url: devtools://devtools/bundled/devtools_app.html). The profile shows a timeline of
the command executions where each execution is assigned to an open slot. The number of slots is determined by the
--concurrency option and the number of open slots is determined by --concurrency minus the number of ongoing
operations. The end result is a visualization of the parallel execution of your commands.

The default location of the performance profile output is at the root of your project.

`sh
$ lerna exec --profile --
`

> Note: Lerna will only profile when topological sorting is enabled (i.e. without --parallel and --no-sort).

$3

You can provide a custom location for the performance profile output. The path provided will be resolved relative to the current working directory.

`sh
$ lerna exec --profile --profile-location=logs/profile/ --
``