chore(deps): update dependency execa to v4.1.0 #30248
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
See the guidelines for reviewing dependency updates for info on how to review dependency update PRs. |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
Updating execa from 1.0.0 to 4.x in the The main breaking changes relevant to us:
I also just think that we've had code that never worked in the
|
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SEE COMMENT FOR DETAILS
This PR contains the following updates:
4->4.1.01.0.0->4.1.04.0.0->4.1.0Release Notes
sindresorhus/execa (execa)
v4.1.0Compare Source
--inspect&--inspect-brkfromexecArgv(#435)8fd3f64v4.0.3Compare Source
timeoutandforceKillAfterTimeoutoptions (#431)9a157b3v4.0.2Compare Source
Bug fixes
bluebird) not working (#427)v4.0.1Compare Source
Bug fixes
Errorinstances (#423)v4.0.0Compare Source
Breaking changes
5a9c76f)stderrandstdouttoerror.message. A new propertyerror.shortMessageis now available to retrieve the error message withoutstderrnorstdout(#397)Bug fixes
childProcess.kill()not working with Electron (#400)v3.4.0Compare Source
Features
serializationoption. That option was added tochild_processmethods in Node.js13.2.0. (#392)v3.3.0Compare Source
Features
windowsHideoption (#388). The option still defaults totrue. However previously it could not be set tofalse.Documentation
Thanks @justsml for helping improving the documentation!
v3.2.0Compare Source
Features
error.signalDescriptionwhich is a human-friendly description of the signal that terminated the child process (if one did). That description is included in error messages as well. (#378)v3.1.0Compare Source
Features
execPathoption which allows changing the path to the Node.js executable to use in child processes. (#377)v3.0.0Compare Source
Breaking changes
bufferoption isfalseandstdoutandstderrare piped, the promise returned byexeca()will resolve only after those streams are fully read. This also applies to theallproperty if thealloption istrue. This concerns you only if you've explicitly set thebufferoption tofalse. (#353)allproperty is nowundefinedunless thealloption is set totrue. (#353)error.exitCodeNamehas been removed. (#375)error.exitCode. Its value was previously based onerror.errnowhich is incorrect. (#375)Features
error.codeproperty when it is defined (#375)error.originalMessageproperty (#373)Bug fixes
detached: trueorcleanup: falseis used (#360)13.0.0-pre(#370)Dependencies
npm-run-pathfrom3.0.0to4.0.0(#376)cross-spawnto7.0.0(#367)Documentation
v2.1.0Compare Source
Features
error.originalMessageproperty (#373)Documentation
Dependencies
7.0.0(#367)v2.0.5Compare Source
Bug fixes
d268fd1v2.0.4Compare Source
Bug fixes
detached: trueorcleanup: falseis used (#360)211febev2.0.3Compare Source
Bug fixes
all(#345)Documentation
v2.0.2Compare Source
Bug fixes
result.allnot being constant across calls (#327, #330)v2.0.1Compare Source
Bug fixes
engines.nodefield inpackage.json. Supported Node versions are either^8.12.0or>=9.7.0(#319, #323)Documentation
execa.command()documentation (#317)v2.0.0Compare Source
Thanks to @GMartigny, @BendingBender, @tomsotte, @ammarbinfaisal, @zokker13, @stroncium, @satyarohith, @bradfordlemley, @coreyfarrell, @brandon93s, @dtinth, @papb for the great features and bug fixes they've contributed!
Please check the Medium article about this release!
Breaking changes
execa.shell()andexeca.shellSync(). Theshelloption should be used instead. (#219)execa.stdout()andexeca.stderr().childProcessResult.stdoutandchildProcessResult.stderrshould be used instead (#234)error.code(numberorstring) in favor oferror.exitCode(number) anderror.exitCodeName(string) (#187, #250)stripeEofoption tostripFinalNewline(f8397ba9, 4d0dc88a, #238)cmd(inchildProcessResultanderror) tocommand(#194)preferLocaloption tofalse. If you are executing locally installed binaries, you'll need to manually specifypreferLocal: true(#314)windowsHideoption is alwaystrue, so that no window pops up on Windows. (8c886452)error.signalis nowundefinedinstead ofnullwhen no signal was used (#193)error.killedtofalsewhen child process timed out (#227)error.killedalways boolean (notundefined) (#229, #248)error.stdoutanderror.stderrare now an empty string (instead ofnull) when the command failed. (#246)Features
execa.command()andexeca.commandSync(). Those are the same asexeca()except both file and arguments are specified in a single string. For example,execa('echo', ['unicorns'])is the same asexeca.command('echo unicorns')(#182, #261, #262, #278, #279, #282)childProcess.allandchildProcessResult.all(#171, #264)execa.node()which (likechild_process.fork()) allows you to execute a Node.js script as a child process (#200, #297, #299, #302, #303, #305, #306).childProcess.kill()does not terminate a child process after 5 seconds, force it by sendingSIGKILL. This can be configured using theforceKillAfterTimeoutoption. (#208, #272, #273, #280, #284, #285)childProcess.cancel()anderror.isCanceled(#189, f24e7c72, #226, #309)error.stdout,error.stderranderror.allnow contain the data that was sent before the child process exit. (#271)error.messageon child process failure (#180, #223, #230, #245, #269).finally()to the child process promise (#174, 65139849)maxBufferoption default value from10 MBto100 MB(#286)Bug fixes
timeoutoption not working as expected (#199)error.timedOutnot working withexeca.sync()(#249)maxBuffererrors not using the same shape as the other errors (#266)extendEndoption not working withshelloption (#184)stripFinalNewlineoption not applied on error properties (#240)/qparameter not added when usingcmdinstead ofcmd.exe(#203)inputoption with a non-executable file (#212, #258)stdiooption cannot be used together withstdin: 0(#301).Documentation
Design
Tests
Maintainers
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.