Toru Nagashima

Ah, sorry. > When there are no scripts matching install:** an error is thrown: ERROR: Task not found: "install:**". I find that this is the main part. Yes, currently `npm-run-all`...

Oh, I'm sorry. I have overlooked this issue. `npm-run-all` is a tool to execute multiple `npm run-script`. Every `npm run-script` is executed in each child process. So `cd` in a...

Thank you for this issue. Could you tell me your environment? (OS, kind of shell, versions of node, npm, ...)

Thanks. I tried to measure time and compare in Ubuntu/bash. Target is [this 'build:babel'](https://github.com/mysticatea/npm-run-all/blob/master/package.json#L26) ``` $ time npm run build:babel ... ... real 0m5.338s user 0m1.755s sys 0m1.032s $ time...

Ah, sorry, I misunderstood this issue.

I'm sorry. Is this the request to add the feature to measure time of tasks? Indeed, it's interesting.

I have often recommended [wait-on](https://www.npmjs.com/package/wait-on) package.

Note: it needs to work in cmd.exe as fallback to basic colors.

@Chalarangelo Thank you very much! Yes, I'm worried how the colors display in `cmd.exe`. The `npm run-script` command uses `cmd.exe` internally on Windows.

Thank you for this issue. Mmm, I don't have WebStorm...