CommandCodeAI / CommandCodeAI/command-code
Supports pnpm/yarn for cmd auto upgrade and the taste cli
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Feature Description
Both tools (command-code and taste) only respects npm, none of them work with pnpm. I always install packages or run packages with pnpm or pnpx, in this case, for command-code, it tries to install a newer version in the background with npm, which causes duplicate packages installed globally, and could potentially take place the installed binary with path sequence.
Also for the taste cli too, use pnpx taste push works, but it also only checks if npm has command-code installed.
Please fix this.
Use Case
No response
Additional Context
No response
How important is this to you?
Important for my workflow
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the command-code and taste CLIs and their auto-upgrade and installed-package checks; start by locating those entry points and tracing where npm is invoked or checked. Done means both tools support pnpm and yarn workflows, including pnpx usage, without relying only on npm.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100