When using standalone pnpm on windows, the pnpm commands open a separate process window.
This is particularly problematic for CI, where process goes missing and CI reports successful step without ever waiting for the response from that process.
pnpm version: 8.4.0
Code to reproduce the issue:
- Install standalone pnpm -
npm i -g @pnpm/exe@latest
- Checkout any repo with
pnpm-lock.yaml (e.g. git clone git@github.com:pnpm/pnpm.git)
- Run
pnpm i --frozen-lockfile
Expected behavior:
- Standalone pnpm runs in the same process window from which it was called
Actual behavior:
- Notice how install process runs on a separate window and the original window reports process as done immediately
Additional information:
node -v prints: Irrelevant since @pnpm/exe comes prebundled with node
- Windows, macOS, or Linux?: Windows
When using standalone pnpm on windows, the pnpm commands open a separate process window.
This is particularly problematic for CI, where process goes missing and CI reports successful step without ever waiting for the response from that process.
pnpm version: 8.4.0
Code to reproduce the issue:
npm i -g @pnpm/exe@latestpnpm-lock.yaml(e.g.git clone git@github.com:pnpm/pnpm.git)pnpm i --frozen-lockfileExpected behavior:
Actual behavior:
Additional information:
node -vprints: Irrelevant since@pnpm/execomes prebundled with node