ehmicky

Hi @jakecastelli, The implementation in [`get-stream`](https://github.com/sindresorhus/get-stream/blob/ee6de5cbcfb0b7e97a18949cad65fa8dea8d6029/source/stream.js#L24) works with Node 18, 20 and 22. However, it would have some subtle differences and breaking changes from the current implementation in [Node.js](https://github.com/nodejs/node/blob/4c3e9659ed116e610d8da8aa0b692cc8c6abb6e4/lib/internal/streams/readable.js#L1357). -...

Hi @ehyland, This seems to be a bug with `@remix-run/node`, not Execa. Namely, the same behavior happens when using `node:child_process` instead of Execa ([TypeScript playground](https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAbwM5gIYHcB2BfOAzKCEOAckwgBMBTALgGMALYAGwoH0xC6qkkSBuALAAoUJFhwARAAEoVEMAAeAWigBXTAHpy1SUOEiUGTAAoSVRhBIAaOAG1zi1OGZUSAXVsIRcOFUwAbjSIPr5wACIAggAqkQBCkQDKAKJsAKoASgAywSRRsQkp6dkkodgi2ACU-EA)). ```ts import {spawn} from 'node:child_process';...

@ehyland Did this fix your issue?

Node.js uses `ProcessEnv` to define both `process.env` and the `env` option of `child_process.spawn()`. Even if `process.env.NODE_PATH` is always defined in Remix, typing `ProcessEnv["NODE_PATH"]` as required means that `env.NODE_PATH` must always...

I created an issue at https://github.com/remix-run/remix/issues/9718

We're working on providing with a patch for this issue at https://github.com/sindresorhus/execa/pull/1141

:wave: I am Execa's co-maintainer. From the look of it, I do not think there is a bug with Execa there, but the issue at https://github.com/sindresorhus/execa/issues/995 can track this. In...

Thanks! Please feel free to post any issue on Execa if you're encountering more bugs, we're very responsive. :) If you do upgrade, you might want to wait for the...

One of Execa's maintainer here :wave: We are looking into fixing this in Execa: https://github.com/sindresorhus/execa/issues/1143

Execa [`9.3.1`](https://github.com/sindresorhus/execa/releases/tag/v9.3.1) should now work. If not, please let us know. :+1: