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
Docs: Installing turborepo local or global #7415
Comments
The primary benefit of global turbo that turbo is able to delegate to the 'local turbo' (whatever is in your repo) meaning anywhere you go you can just do |
Thanks @arlyon. In my project I have started using |
Good news: I'm doing a nearly-full rewrite of our documentation and this is something that I've already done. I'll come back and close this when it's shipped. |
Ahhh amazing. Thanks a ton @anthonyshew! |
Thanks @anthonyshew this is solves all my problems. Feel free to close the issue or keep it open to track it. This reads much better with the intro paragraph introducing both ways to install. |
What is the improvement or update you wish to see?
As a developer reading this page I was confused why I am being recommended up front to install turborepo globally. It does this multiple times in the documentation. Reading the install page down the very bottom in the "Install per repository" section it recommends installing it as a dev dependency and says "You may wish to pin the version of Turborepo used within a repository, especially if you are collaborating with other developers. In that case, add turbo as a dev dependency at the root of the repository:"
Is there any context that might help us understand?
I would assume the majority of developers are using turborepo with other developers and would want to benefit from remote-caching. Could this become the default or can we add a better reason why global is the recommended way to install the package.
Does the docs page already exist? Please link to it.
https://turbo.build/repo/docs/installing
The text was updated successfully, but these errors were encountered: