Sign Up for Free

RunKit +

Try any Node.js package right in your browser

This is a playground to test code. It runs a full Node.js environment and already has all of npm’s 400,000 packages pre-installed, including @lerna/global-options with all npm packages installed. Try it out:

var globalOptions = require("@lerna/global-options")

This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.

@lerna/global-options v3.13.0

Global options applicable to _every_ lerna sub-command

@lerna/global-options

Global options applicable to every lerna sub-command

Options

--concurrency

How many threads to use when Lerna parallelizes the tasks (defaults to count of logical CPU cores)

$ lerna publish --concurrency 1

--loglevel <silent|error|warn|success|info|verbose|silly>

What level of logs to report. On failure, all logs are written to lerna-debug.log in the current working directory.

Any logs of a higher level than the setting are shown. The default is "info".

--max-buffer <bytes>

Set a max buffer length for each underlying process call. Useful for example when someone wants to import a repo with a larger amount of commits while running lerna import. In that case the built-in buffer length might not be sufficient.

--no-progress

Disable progress bars. This is always the case in a CI environment.

--no-sort

By default, all tasks execute on packages in topologically sorted order as to respect the dependency relationships of the packages in question. Cycles are broken on a best-effort basis in a way not guaranteed to be consistent across Lerna invocations.

Topological sorting can cause concurrency bottlenecks if there are a small number of packages with many dependents or if some packages take a disproportionately long time to execute. The --no-sort option disables sorting, instead executing tasks in an arbitrary order with maximum concurrency.

This option can also help if you run multiple "watch" commands. Since lerna run will execute commands in topologically sorted order, it can end up waiting for a command before moving on. This will block execution when you run "watch" commands, since they typically never end. An example of a "watch" command is running babel with the --watch CLI flag.

--reject-cycles

Fail immediately if a cycle is found (in bootstrap, exec, publish or run).

$ lerna bootstrap --reject-cycles
RunKit is a free, in-browser JavaScript dev environment for prototyping Node.js code, with every npm package installed. Sign up to share your code.
Sign Up for Free