feat(core): introduce the NX_PROJECT_GRAPH_CACHE_DIRECTORY to allow s… #10693
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.
…eparating it from the computation cache
Current Behavior
When using shared volumes, different consumers of the cache can write a different project graph to the cache, overwriting one that may be in use by other consumers. There is no way to separate that cache from the computation cache.
Expected Behavior
When using shared volumes, use the
NX_PROJECT_GRAPH_CACHE_DIRECTORY
environment to dictate where Nx should store the project graph cache (and the daemon).Related Issue(s)
Fixes #10000
Closes #10608