Skip to content
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

PNPM commands with --kill-others cause concurrently to exit error #531

Open
dr3 opened this issue Feb 19, 2025 · 0 comments
Open

PNPM commands with --kill-others cause concurrently to exit error #531

dr3 opened this issue Feb 19, 2025 · 0 comments

Comments

@dr3
Copy link

dr3 commented Feb 19, 2025

What

When trying to kill-others concurrently exits unhappy when the command its killing is a pnpm script

Reproduction

Create a dir with this package.json, node 20+ & pnpm 9.15.4

{
  "name": "concurrently-example",
  "scripts": {
    "one": "sleep 30 && exit 1",
    "two": "sleep 2 && exit 0",
    "this-fails": "concurrently --success=first --kill-others \"pnpm two\" \"pnpm one\"",
    "this-passes": "concurrently --success=first --kill-others \"sleep 2 && exit 0\" \"sleep 30 && exit 1\""
  },
  "dependencies": {
    "concurrently": "9.1.2"
  }
}

Running pnpm this-fails returns ELIFECYCLE  Command failed.
Image

Running pnpm this-passes is happy
Image

Debug

This works as expected switching to use npm
I debated if this is a concurrently bug, or a pnpm one, but In the end, concurrently should probably be able to handle killing any kind of process in isolation

@dr3 dr3 changed the title PNPM commands with --kill-others fails cause concurrently to exit error PNPM commands with --kill-others cause concurrently to exit error Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant