-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use proc-log
for stdout and stderr
#7373
Conversation
proc-log
and @npmcli/run-script
deps
09526ae
to
0b77f20
Compare
proc-log
and @npmcli/run-script
depsproc-log
out stdout and stderr
0b77f20
to
f2e0073
Compare
proc-log
out stdout and stderrproc-log
for stdout and stderr
61ea31c
to
dedb25e
Compare
e612ae9
to
d9985cc
Compare
|
The breaking change commits for libnpmversion and libnpmpack need |
I'm not sure what combination of install commands caused |
LGTM. update the comment, rebase/squash, and I'll approve it. Thanks for taking it in steps w/ TODOS. |
fd62344
to
5ce9e08
Compare
BREAKING CHANGE: libnpmexec now emits an output event on process instead of invoking the output function passed in
BREAKING CHANGE: libnpmversion no longer takes a `silent` option to suppress output from `@npmcli/run-script`. That output is now emitted via an `output` event on `process`.
BREAKING CHANGE: libnpmpack no longer takes a `silent` option to suppress output from `@npmcli/run-script`. That output is now emitted via an `output` event on `process`.
5ce9e08
to
0bd87c4
Compare
@wraithgar I added |
TODO
pacote@18
deps: bump @npmcli/run-script from 7.0.4 to 8.0.0 pacote#352pacote
If feat: addFor a later PRtime
andinput
proc-log#80 lands we can make theread()
related breaking changes here (or in a following PR before the next release) to minimize major versions oflibnpmexec
.