npm-run-all

npm-run-all copied to clipboard

process exits before output emitted

1

I'm running some linting and tests in a docker container with `npm-run-all -pn --silent --aggregate-output lint:* test` The output is as I expect except that it cuts off early because...

ezpuzz

[Question] performance between flat npm-run-all -p vs nested npm-run-all -p

1

I was wondering if there were any comparison done for performance between flat npm-run-all -p vs nested npm-run-all -p. Let's say I have 100 tasks/commands. I can do npm-run-all -p...

dereklin

Feature request: Abort all tasks in Node API

6

I'm trying to use the Node API to keep some tasks running in the background, while other tasks are performed. Once the other tasks are finished, I'd like to abort...

tobiastom

In documentation for npm-run-all (https://github.com/mysticatea/npm-run-all/blob/master/docs/npm-run-all.md) is missing documentation for default values for arguments. I found the functionality described in https://github.com/mysticatea/npm-run-all/blob/master/test/argument-placeholders.js.

WuDo

use unix tools if available in windows

1

I use git-bash (like probably nearly all windows npm user). if i run `mkdir -p plop` it create me `plop` folder if not existant and do nothing if it exist....

1000i100

Support request: order of execution with wildcard

2

When you use the glob pattern to run tasks in sequence (ie. with run-s): `npm-run-all` build:* what's the expected order of execution ?

gunzip

Custom labels

2

We would like to use the `--print-labels` option, but when giving `npm-run-all` extra arguments (for example `npm-run-all --print-labels \"build -- --watch\" [...]`), this prints very long labels that add clutter...

astorije

Pass same param to scripts

1

Can I pass one (or more) same arguments to all scripts in run-all? ``` "foo:1": "ng build foo1", "foo:2": "ng build foo2", "foos": "npm-run-all foo:* -- --enviroment=staging" ``` So it...

dzolnjan

I had an issue using the node API when I'm building a CLI tool since the api reads the `package.json` from the current folder ([here](https://github.com/mysticatea/npm-run-all/blob/52eaf86242ba408dedd015f53ca7ca368f25a026/lib/read-package-json.js#L21)) I can't execute my CLI...

kariae

Misbehaving processes aren't killed with --race

3

Given the following `package.json` file (cruft removed): ```json { "scripts": { "a": "test/programs/a", "b": "test/programs/b", "sleep10s": "sleep 10" }, "devDependencies": { "npm-run-all": "^4.1.3" } } ``` Racing `a`, `b`, and...

whymarrh