Leverage Node 22.3.0's `node --run` for `run-s` when possible.

[jdalton]

semver.satisfies(process.versions.node, '>=22.3.0')

There could even be a separate node-s for the https://nodejs.org/api/cli.html#--run command. It does have limitations though so making it a separate command that falls back to a more run-s kind of command would be nice. The speed up is very nice.

[voxpelli]

The differences between pnpm, yarn, npm are already challenging – this feels a bit like one more standard 😂

That said, it could be a benefit that it has less features

(Someone should do a write up of the differences between them all so that we could ideally arrive at a standard for npm scripts with maybe two levels "lightweight" runner like node --run and "full featured" like the others, and ensure that the full featured ones are compatible with each other and a strict superset of the lightweight one and as such also compatible with it)

[bcomnes]

I would be nervous to default to it initially, but maybe we could flag it?

[bcomnes]

Got another request for this today from @nolanlawson after noticing that when running with pnpm run, there is quite a large overhead per parallel task. I'm thinking we could add a flag thats like --force-node-run or something that when it does runner selection, it will default to node run. Of course, this will add another layer of arg passing inconsistency, but maybe we can correct for it in this case.

[achou11]

Got another request for this today from @nolanlawson after noticing that when running with pnpm run, there is quite a large overhead per parallel task. I'm thinking we could add a flag thats like --force-node-run or something that when it does runner selection, it will default to node run. Of course, this will add another layer of arg passing inconsistency, but maybe we can correct for it in this case.

This would be super helpful. I'm currently dealing with a performance regression in npm script execution between Node 22.17.1 and Node 22.18.0 that I suspect has to do with npm's cli (npm/cli#8533). My hope is that being able to avoid using npm to run the scripts would help sidestep that issue 😅

[bcomnes]

Yikes, sad to hear that.