[BUG] 10.6.0 regresses stdout pollution on npx/npm exec
lorenzogrv opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
npm pollutes stdtout when using npx/npm exec
Old behavior:
$ npm --version
10.2.4
$ npm exec -- /bin/bash -c 'echo what?'
what?$ npm install -g npm@latest
removed 43 packages, and changed 74 packages in 710ms
24 packages are looking for funding
run `npm fund` for detailsNew behavior
$ npm --version
10.6.0
$ npm exec -- /bin/bash -c 'echo what?'
> @grupomarea/roo@0.1.0 npx
> /bin/bash -c echo what?
what?This seems similar to #7354
Expected Behavior
$ npm --version
10.6.0
$ npm exec -- /bin/bash -c 'echo what?'
what?Steps To Reproduce
- Follow the steps above
Environment
- system
$ cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=21.1
DISTRIB_CODENAME=vera
DISTRIB_DESCRIPTION="Linux Mint 21.1 Vera"
$ uname -i
x86_64- npm config:
; node version = v20.11.1
; npm version = 10.6.0For a sake of completeness, this does not happen on 10.5.0
$ npm install -g npm@10.5
# ...
$ npm exec -- /bin/bash -c 'echo what?'
what?PS: Why v10.6.0 is tagged @latest when current docs changelog states v10.5.2 is latest CLI?
@wraithgar seems also related to npm/statusboard#829
No Problem. Thank you for testing with latest npm.