manifoldco / manifoldco/torus-cli
Bug - out of date package torus stepping on global
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 603
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
If you have installed Torus globally (using `brew install` or `npm install -g`), and then install torus locally as a package in your `package.json`. If the versions between the two get out of sync they'll step on one another resulting in a user always being asked to login.
Contributor guide
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
Start by reproducing the conflict between globally installed Torus and the local package when their versions differ, using both the Homebrew or npm installation paths described. Trace how the CLI selects or invokes the global and local installations, then verify that mismatched versions no longer cause repeated login prompts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nodejs
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100