Open AlexanderKlump opened 3 hours ago
We've the fixed the internal process init logic, that previously blocked pid obtaining: in short cp.spawn
is not wrapped with setImmediate
workaround anymore.
$({quiet: true})cmd
applies the option before the first log event may occur, meanwhile $cmd
.quiet() modifies the behavior or the running process.
@AlexanderKlump , Here's this specific piece. If you have any ideas on how to soften the subtle side effects, share them with us plz.
Testing the latest change from version 8.1.9 to 8.2.0 we detected some unexpected change of behavior in the output of our scripts working with zx. I tried to reproduce the observed behavior in the following TS script, which I run with
node --loader ts-node/esm --no-warnings=ExperimentalWarning testZx.ts
and my node version isv20.10.0
.With zx version 8.1.9 the output is:
Observations:
$.verbose = false
and$.quiet = false
output nothing$.verbose = true
and$.quiet = false
output the zx command and its outputWith zx version 8.2.0 we get this:
Observations:
$.verbose = true & $.quiet = false & .verbose(false)
have a different behavior as$.verbose = false
and$.quiet = false
For me this looks like an unintended behavior, or do I misperceive something?