Toru Nagashima

Thank you for this issue! Sounds reasonable. I need to check the direction of standard cancelable promise proposal in order to think proper API. https://github.com/tc39/proposals#readme

Sadly, the standard of cancelable promises has been withdrawn :cry: . I will consider my own spec. https://github.com/tc39/proposals/commit/37e3c5a157e7b3a8211e2e0bb85c9f612b0f04fc

I don't think that the `promise.cancel` method is the right direction. Browsers use [AbortController](https://developer.mozilla.org/en-US/docs/Web/API/AbortController) to abort asynchronous operations. This has been standardized already. ECMAScript is following that, cancellation API is...

Thank you for this issue. Though I might not understand this issue, I think there are some solutions: ``` npm-run-all -s lint -p build:* ``` ``` npm run lint &&...

Thank you for this issue. To run a server then run tests, I recommend a use of [wait-on](https://www.npmjs.com/package/wait-on) command. This example may help you: https://github.com/mysticatea/npm-run-all/issues/72#issuecomment-272430044

Thank you for this issue. I have not tried such a many tasks. In general, `npm-run-all` spawns `npm run-script xxx` process and the spawned `npm run-script xxx` process spawns a...

Thank you for the question. It executes tasks in definition order in package.json.

Thank you for your question. No. This is a tool to run multiple npm-scripts in series or parallel.

Therefore, `run-s 'echo 1'` means "run 'echo' task with an argument `1`."

``` /bin/sh: -c: line 0: syntax error near unexpected token `(' /bin/sh: -c: line 0: `run-p install:*(**)' ``` Thank you for your report. But it looks the error that `/bin/sh`...