Release v10.2.0 · sindresorhus/execa

These are bug fixes, but they might affect code that relied on the previous incorrect behavior.

Exceeding maxBuffer now terminates the subprocess with killSignal, instead of leaving it running and the promise pending f6de9be
maxBuffer: 0 now limits the output of synchronous methods, like asynchronous methods 224dd20
Options of $ set to undefined now use $'s defaults, such as inheriting stdin f61a6e9

Fix invalid file descriptor objects, such as closed file handles, crashing the current process instead of throwing d0a5968
Fix synchronous transforms: errors being hidden, filtered output being returned on failure, mixed text and byte chunks being reordered, and final() being skipped without input 0ba2b6e ed80079 9c54833
Fix result.all changing objects when only stdout or stderr is buffered 8629132
Fix writing objects to a web WritableStream 5ea2900
Fix an invalid subprocess.duplex() option making later stream conversions hang 5e4345b
Fix execaNode() not running its file when the current process uses --print e747872

Fix result and subprocess types when the options are a union, including IPC f5772f3 355d917 cb8aaf6
Fix result types when options bound with execa(options) are overridden or reset with undefined 708fed7
Fix subprocess.stdin types with the input and inputFile options 236c831
Fix chunk types of subprocess.iterable() with object-mode transforms a2912e5
Fix fd-specific option types, and execaNode() types with node: undefined 80b01e9 523cf9b

Navigation Menu