execa

This is a bug with Node.js, described in https://github.com/nodejs/node/issues/42923#issuecomment-2762174940 Let's see how the discussion on the Node.js repository goes before deciding on any workaround.

Being able to spawn a worker thread instead of a child process using a simple boolean option would be nice. Unlike in browsers, Node.js includes many similar features as child processes: environment variables, //, . Also, most of Execa's logic is actually userland, i.e. implemented by us and not borrowed from . For example, most things input/output-related (including subprocess piping), the verbose mode, etc. It would be nice to be able to re-use all of those Execa features but with a worker thread instead. I believe 90-95% of features can be re-used. This option would imply the option, since only Node.js files can be launched as threads. Instead of returning a property (#413), this would return a property, with the instead. We would try to make the properties/methods as close to as possible, for parity. That's a bigger feature, but this might be quite useful. What are your thoughts on this @sindresorhus?

Fixes #578