-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Rename go module to allow command line installs #327
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/vercel/turbo-site/2GRstQRH3MyhQE86TzwPzkCeodJZ |
I think this complicates #397 quite a bit? |
we should do it for the go doc though I guess |
I think you could probably work out if the binary is in $GOBIN and prompt for go install for the latest version in that instance? |
We should do this, but probs easier to just take main and search + replace at this point. |
Yeah. Almost certainly is. I'll get it rebased on Monday for you. Update: rebased this now. |
The `go install` command doesn't like it when the go.mod file declares a different path to the module, to the actual path. e.g. ``` $ go install github.com/vercel/turborepo/cli/cmd/turbo@latest go install: github.com/vercel/turborepo/cli/cmd/turbo@latest: github.com/vercel/turborepo/[email protected]: parsing go.mod: module declares its path as: turbo but was required as: github.com/vercel/turborepo/cli ``` This PR renames the go module to match the path name, as go expects. This allows the turborepo CLI to be installed via `go install`
so we don't really have to benchmark that
The
go install
command doesn't like it when the go.mod filedeclares a different path to the module, to the actual path.
e.g.
This PR renames the go module to match the path name, as go expects. This allows the turborepo CLI to be installed via
go install