Skip to content

bug: CLI not usable from PNPM #1311

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

Closed
davidchalifoux opened this issue Sep 16, 2024 · 3 comments
Closed

bug: CLI not usable from PNPM #1311

davidchalifoux opened this issue Sep 16, 2024 · 3 comments

Comments

@davidchalifoux
Copy link

Provide environment information

System:
OS: macOS 15.0
CPU: (14) arm64 Apple M3 Max
Memory: 2.70 GB / 36.00 GB
Shell: 5.9 - /bin/zsh

Binaries:
Node: 20.15.1 - ~/.nvm/versions/node/v20.15.1/bin/node
npm: 10.7.0 - ~/.nvm/versions/node/v20.15.1/bin/npm
pnpm: 9.10.0 - /opt/homebrew/bin/pnpm
bun: 1.1.24 - ~/.bun/bin/bun

Describe the bug

Calling the CLI through pnpm dlx is not working because it detects multiple executable binaries.

> pnpm dlx [email protected] dev

 ERR_PNPM_DLX_MULTIPLE_BINS  Could not determine executable to run. trigger.dev has multiple binaries: triggerdev, trigger

Try one of the following:
pnpm --package=trigger.dev dlx triggerdev
pnpm --package=trigger.dev dlx trigger

When trying the recommended solution from PNPM of specifying the package, the CLI fails.

> pnpm --package=trigger.dev dlx [email protected] deploy --env staging --skip-typecheck

 ENOENT  Command failed with ENOENT: [email protected] deploy --env staging --skip-typecheck
spawn [email protected] ENOENT

pnpm: Command failed with ENOENT: [email protected] deploy --env staging --skip-typecheck
spawn [email protected] ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
 ELIFECYCLE  Command failed with exit code 254.

Reproduction repo

https://stackblitz.com/edit/stackblitz-starters-vyz9ci?file=package.json

To reproduce

Check out the Stackblitz example and try running these commands:

  • pnpm run example1
  • pnpm run example2

Additional information

No response

@ericallam
Copy link
Member

Thanks for this detailed report, will get it fixed up ASAP 🫡

@ericallam
Copy link
Member

This has been fixed in 2b5771f and released as 3.0.2

@davidchalifoux
Copy link
Author

Can confirm it's working now, thanks!

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

2 participants