execa v3.0.0

Version Release Notes from October 14, 2019 (over 4 years ago)

« Changelog History

execa v3.0.0 Release Notes

Release Date: 2019-10-14 // over 4 years ago

💥 Breaking changes
- 🖨 When the buffer option is false and stdout and stderr are piped, the promise returned by execa() will resolve only after those streams are fully read. This also applies to the all property if the all option is true. This concerns you only if you've explicitly set the buffer option to false. (#353)
- The all property is now undefined unless the all option is set to true. (#353)
- 🚚 error.exitCodeName has been removed. (#375)
- Fix error.exitCode. Its value was previously based on error.errno which is incorrect. (#375)
🔋 Features
- Do not remove error.code property when it is defined (#375)
- 👌 Improve error messages (#375)
- ➕ Add error.originalMessage property (#373)
🐛 Bug fixes
- 🛠 Fix errors being thrown when detached: true or cleanup: false is used (#360)
- 👉 Make execa compatible with Node.js 13.0.0-pre (#370)
Dependencies
- ⬆️ Upgrade npm-run-path from 3.0.0 to 4.0.0 (#376)
- ⬆️ Upgrade cross-spawn to 7.0.0 (#367)
📚 Documentation
- Document the reasons why the returned promise might fail (#364)

Awesome Node.js is part of the LibHunt network. Terms. Privacy Policy.