TASK: Update dependency execa to v7 #885
Open
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.
This PR contains the following updates:
1.0.0
->7.1.1
Release Notes
sindresorhus/execa (execa)
v7.1.1
Compare Source
Features
$.sync(options)`command`
is used instead of$(options).sync`command`
(#551)Bug fixes
$`command argument${value}`
(#553)stdin
option when using$`command`
: it should beinherit
(#550)v7.1.0
Compare Source
Features
$
method to write Node.js scripts like zx. For more information, please see this blog post, this section and this page. Thanks @aaronccasanova for this great feature!.pipeStdout()
,.pipeStderr()
and.pipeAll()
methods to redirectstdout
/stderr
to a file, a stream or another process.inputFile
option to use a file asstdin
.verbose
option to print each command onstderr
before executing it. This can also be enabled by setting theNODE_DEBUG=execa
environment variable in the current process.v7.0.0
Compare Source
Breaking
a09cbc0
Fixes
end
event on streams when process fails (#518)30c7a7a
execaNode
signature inindex.d.ts
(#506)1f7677c
v6.1.0
Compare Source
AbortController
(#490)c6e791a
cwd
andlocalDir
options to be URLs (#492)93ab929
v6.0.0
Compare Source
Breaking
7707880
require('execa')
→import {execa} from 'execa'
require('execa').sync
→import {execaSync} from 'execa'
require('execa').command
→import {execaCommand} from 'execa'
require('execa').commandSync
→import {execaCommandSync} from 'execa'
require('execa').node
→import {execaNode} from 'execa'
v5.1.1
Compare Source
2b9c0e1
v5.1.0
Compare Source
.escapedCommand
property to the results (#466)712bafc
v5.0.1
Compare Source
timeout
option validation (#463)427c5c2
v5.0.0
Compare Source
Breaking
bdbd975
This is only a breaking change if you depend on the exact error message.
Improvements
5d64878
v4.1.0
Compare Source
--inspect
&--inspect-brk
fromexecArgv
(#435)8fd3f64
v4.0.3
Compare Source
timeout
andforceKillAfterTimeout
options (#431)9a157b3
v4.0.2
Compare Source
Bug fixes
bluebird
) not working (#427)v4.0.1
Compare Source
Bug fixes
Error
instances (#423)v4.0.0
Compare Source
Breaking changes
5a9c76f
)stderr
andstdout
toerror.message
. A new propertyerror.shortMessage
is now available to retrieve the error message withoutstderr
norstdout
(#397)Bug fixes
childProcess.kill()
not working with Electron (#400)v3.4.0
Compare Source
Features
serialization
option. That option was added tochild_process
methods in Node.js13.2.0
. (#392)v3.3.0
Compare Source
Features
windowsHide
option (#388). The option still defaults totrue
. However previously it could not be set tofalse
.Documentation
Thanks @justsml for helping improving the documentation!
v3.2.0
Compare Source
Features
error.signalDescription
which 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.0
Compare Source
Features
execPath
option which allows changing the path to the Node.js executable to use in child processes. (#377)v3.0.0
Compare Source
Breaking changes
buffer
option isfalse
andstdout
andstderr
are piped, the promise returned byexeca()
will resolve only after those streams are fully read. This also applies to theall
property if theall
option istrue
. This concerns you only if you've explicitly set thebuffer
option tofalse
. (#353)all
property is nowundefined
unless theall
option is set totrue
. (#353)error.exitCodeName
has been removed. (#375)error.exitCode
. Its value was previously based onerror.errno
which is incorrect. (#375)Features
error.code
property when it is defined (#375)error.originalMessage
property (#373)Bug fixes
detached: true
orcleanup: false
is used (#360)13.0.0-pre
(#370)Dependencies
npm-run-path
from3.0.0
to4.0.0
(#376)cross-spawn
to7.0.0
(#367)Documentation
v2.1.0
Compare Source
Features
error.originalMessage
property (#373)Documentation
Dependencies
7.0.0
(#367)v2.0.5
Compare Source
Bug fixes
d268fd1
v2.0.4
Compare Source
Bug fixes
detached: true
orcleanup: false
is used (#360)211febe
v2.0.3
Compare Source
Bug fixes
all
(#345)Documentation
v2.0.2
Compare Source
Bug fixes
result.all
not being constant across calls (#327, #330)v2.0.1
Compare Source
Bug fixes
engines.node
field inpackage.json
. Supported Node versions are either^8.12.0
or>=9.7.0
(#319, #323)Documentation
execa.command()
documentation (#317)v2.0.0
Compare 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()
. Theshell
option should be used instead. (#219)execa.stdout()
andexeca.stderr()
.childProcessResult.stdout
andchildProcessResult.stderr
should be used instead (#234)error.code
(number
orstring
) in favor oferror.exitCode
(number
) anderror.exitCodeName
(string
) (#187, #250)stripeEof
option tostripFinalNewline
(f8397ba9, 4d0dc88a, #238)cmd
(inchildProcessResult
anderror
) tocommand
(#194)preferLocal
option tofalse
. If you are executing locally installed binaries, you'll need to manually specifypreferLocal: true
(#314)windowsHide
option is alwaystrue
, so that no window pops up on Windows. (8c886452)error.signal
is nowundefined
instead ofnull
when no signal was used (#193)error.killed
tofalse
when child process timed out (#227)error.killed
always boolean (notundefined
) (#229, #248)error.stdout
anderror.stderr
are 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.all
andchildProcessResult.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 theforceKillAfterTimeout
option. (#208, #272, #273, #280, #284, #285)childProcess.cancel()
anderror.isCanceled
(#189, f24e7c72, #226, #309)error.stdout
,error.stderr
anderror.all
now contain the data that was sent before the child process exit. (#271)error.message
on child process failure (#180, #223, #230, #245, #269).finally()
to the child process promise (#174, 65139849)maxBuffer
option default value from10 MB
to100 MB
(#286)Bug fixes
timeout
option not working as expected (#199)error.timedOut
not working withexeca.sync()
(#249)maxBuffer
errors not using the same shape as the other errors (#266)extendEnd
option not working withshell
option (#184)stripFinalNewline
option not applied on error properties (#240)/q
parameter not added when usingcmd
instead ofcmd.exe
(#203)input
option with a non-executable file (#212, #258)stdio
option 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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.