
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@qoopido/lerna.exec
Advanced tools
Lerna-Lite Exec command will execute an arbitrary command in each package
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 :)).
npm install @qoopido/lerna.exec -D -W
# then use it (see usage below)
lerna exec <command>
$ lerna exec -- <command> [..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:
$ 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:
$ lerna exec -- node \$LERNA_ROOT_PATH/scripts/some-script.js
lerna exec accepts all filter flags.
$ lerna exec --scope my-component -- ls -la
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:
$ lerna exec --concurrency 1 -- ls -la
--dry-runDisplays the execution command that would be performed without actually executing it. This could be helpful for troubleshooting.
$ lerna exec echo hello world --dry-run
--streamStream output from child processes immediately, prefixed with the originating package name. This allows output from different packages to be interleaved.
$ lerna exec --stream -- babel src -d lib
--parallelSimilar 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.
$ lerna exec --parallel -- babel src -d lib -w
Note: It is advised to constrain the scope of this command when using the
--parallelflag, as spawning dozens of subprocesses may be harmful to your shell's equanimity (or maximum file descriptor limit, for example). YMMV
--no-bail# Run a command, ignoring non-zero (error) exit codes
$ lerna exec --no-bail <command>
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.
--no-prefixDisable 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.
--profileProfiles 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.
$ lerna exec --profile -- <command>
Note: Lerna will only profile when topological sorting is enabled (i.e. without
--paralleland--no-sort).
--profile-location <location>You can provide a custom location for the performance profile output. The path provided will be resolved relative to the current working directory.
$ lerna exec --profile --profile-location=logs/profile/ -- <command>
FAQs
Lerna-Lite Exec command will execute an arbitrary command in each package
We found that @qoopido/lerna.exec demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.