Post

Nice that you mention the `node --run` alternative. It doesn’t solve the cross-env situation, but I kinda like it nonetheless. It looks cleaner to cut put the package manager when running these scripts.

Is the cost of running these negligible in already compatible environments like GH Workflows, Docker etc.? I guess I shouldn’t be overthinking this, pnpm v12 is fast AF

I might be overthinking it, but it strikes me that this would mean that, in an attempt to write portable code (platform), one would write non-portable code (package manager).

So, should scripts entries be (optional) objects? And how do we express chaining with && and ||? 😎 ``` "scripts": { "test": { "command": "...", "args": [], "env": { "VAR": "VALUE" } } } ```