fregante

The problem here isn't `cross-env` but the fact that variables aren't shared across tasks ```json { "set": "HI=hello", "use": "echo $HI stranger" } ``` ```sh $ npm-run-all set use stranger...

This is interesting but consider that each test would mean `npm i && npm test` and they can probably take a whole minute, only to _suggest_ a version you have...

`npm` exposes a useful method: `require('npm/libs/pack').getContents()` From this I think it's a matter of testing `pkg.bin in getContents()` and such

Here: https://github.com/typicode/pkg-ok Apparently it's pretty old, even

- Related/similar: https://github.com/sindresorhus/type-fest/issues/115

It uses `minimatch` under the hood, so you can already use negated patterns. In your case: ```sh run-s test:!(foo) ``` Demo: ```sh ❯ run-s 'wow:*' > @ wow:a > echo...

This shouldn't be part of `npm-run-all`. There's already the native `sleep` on most OSs and you can use `delay-cli` if you want a cross-platform version. Or even the excellent `wait-on`,...

You’re right about `&`, but `$tsc` or `$ tsc` would also make sense. The latter can already be added if you have an npm script named `$` with command `bash...

What if `npm-run-all` simply had a *default* `$` script? I think that would be easy to implement and explain. The point here would be to avoid adding further scripts to...

> Here, the bot adds a huge comment in every PR. The bot is made by humans. Tell the humans to tell the bot to wrap it all in a...