npm-run-all
npm-run-all copied to clipboard
A CLI tool to run multiple npm-scripts in parallel or sequential.
I use `npm-run-all` to run multiple commands in parallel, but currently the commands can only be npm scripts. This is usually fine if you need these commands directly accessible (e.g....
### What is it? This adds a new placeholder, `{%}`, which unfolds into multiple tasks – one for each input argument. The unfolded tasks gets assigned `{1}`, `{2}` etc instead...
To resolve #175 I have added an option --report-by-task. If this option is true, two reports are created for each task: (task).out and (task).err The existing tests all pass. I...
I'm using the npm-run-all api to run some tasks in parallel. I want to redirect the output of each task to a separate file, so I can't use the stdout...
``` json { "scripts": { "set-env:test": "cross-env NODE_ENV=test", "set-env:staging": "cross-env NODE_ENV=staging", "set-env:production": "cross-env NODE_ENV=production", "deploy:managers": "node ./deployment-scripts/deploy-managers", "deploy:managers:test": "npm-run-all set-env:test deploy:managers" } } ``` When I run `deploy:managers:test` script I...
Feature request for a flag to specify delay when two or more tasks should run in parallel. For case when two or more tasks has to be running simultaneously, but...
Resolves #121 Still todo: - [ ] Documentation of new `--labels` option - [ ] Unit test updates
The following should print hello after running test but doesn't. ``` echo hello | ( node_modules/.bin/run-p test; cat ) ``` `run-p` should not read from stdin unless it's using it....
Not having prefix every command with `npm run` is very convenient but it does force you do alias every command for use in `npm-run-all`. For example the following script: ```...
It will be awesome if the array of commands could be objects that can have different specific settings. In my case I need to set different streams for each process...