docs: nx remote caching has changed to be free like Turborepo #10460
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
turbo-orchestrator
bot
added
area: docs
JamesHenry
changed the title
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@JamesHenry is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
anthonyshew
requested changes
May 8, 2025
anthonyshew
changed the title
anthonyshew
changed the title
|
Thank you! |
anthonyshew
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The deleted statement was never accurate in Nx. We briefly openly explored some alternative solutions and pricing structures for self-hosted caching but this never landed as a requirement in Nx. We took on the feedback loud and clear that our initial thinking was misguided and we changed course before it landed.
We offer a broader array of free cache hosting options than Turborepo, with the OpenAPI spec being the exact equivalent of how Turborepo chooses to approach the problem, you can learn more here:
https://nx.dev/recipes/running-tasks/self-hosted-caching
For this change, I went for the most generous correction I could, but you may decide the overall section is redundant without this key incorrect point.
While I'm here, I'd suggest you run through this guide yourself again because it doesn't really make sense currently. If you run the command you have listed Nx generates package manager workspaces, no
project.jsonfiles, andpackage.jsonfiles for each project, but then you tell people to add these things because that's "only how Turborepo does things" (not quoting but that's the inaccurate gist)...Finally, as pointed out last time your
nx.jsontoturbo.jsoncomparison is very, very far from apples to apples. On the nx side you are demonstrating the configuration of a bunch of capabilities that Turborepo simply does not have and then saying "see, look, nx requires more config", which doesn't seem fair 🤷Nx can work exactly how Turborepo works, and it can also work with optional plugins, users have complete freedom of choice. If you'd like to collaborate on further rewrites I'm totally open to that, but I thought I would keep this PR very focused on this critical correction for now.