From f4bc24006423604f70fbf03bbeb9dfb5f2cd6295 Mon Sep 17 00:00:00 2001 From: Jack Hsu Date: Thu, 16 Sep 2021 13:36:58 -0400 Subject: [PATCH] docs(core): update broken link; wrap nx-dev serve command with npx so ts-node does not need to be available globally (#7030) --- docs/shared/computation-caching.md | 2 +- nx-dev/nx-dev/project.json | 2 +- .../public/documentation/latest/shared/computation-caching.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/shared/computation-caching.md b/docs/shared/computation-caching.md index 601ce405d5234..2599f2049ed0f 100644 --- a/docs/shared/computation-caching.md +++ b/docs/shared/computation-caching.md @@ -124,7 +124,7 @@ If the outputs property is missing, Nx defaults to caching the appropriate folde By default, Nx uses a local computation cache. **Because the word "cache" appears in the description, the phrase "artifact caching" comes to mind. But this isn't the right way to think about it. What Nx does is really computation memoization.** Nx doesn't choose to use or not use the cached value. There are no versions. It is transparent: Nx skips the computation only when running the computation would have produced the same result. -Nx stores the cached values only for a week, after which they are deleted. To clear the cache, delete the [cache directory](customizing-the-cache-location), and Nx creates a new one the next time it tries to access it. +Nx stores the cached values only for a week, after which they are deleted. To clear the cache, delete the [cache directory](#customizing-the-cache-location), and Nx creates a new one the next time it tries to access it. ## Distributed Computation Caching diff --git a/nx-dev/nx-dev/project.json b/nx-dev/nx-dev/project.json index d551818e842bf..130c1b1fffee6 100644 --- a/nx-dev/nx-dev/project.json +++ b/nx-dev/nx-dev/project.json @@ -28,7 +28,7 @@ "outputs": [], "options": { "commands": [ - "ts-node -P ./scripts/tsconfig.scripts.json ./scripts/documentation/nx-dev-docs-latest-sync.ts --watch", + "npx ts-node -P ./scripts/tsconfig.scripts.json ./scripts/documentation/nx-dev-docs-latest-sync.ts --watch", "nx run nx-dev:serve-nextjs" ], "parallel": true diff --git a/nx-dev/nx-dev/public/documentation/latest/shared/computation-caching.md b/nx-dev/nx-dev/public/documentation/latest/shared/computation-caching.md index 601ce405d5234..2599f2049ed0f 100644 --- a/nx-dev/nx-dev/public/documentation/latest/shared/computation-caching.md +++ b/nx-dev/nx-dev/public/documentation/latest/shared/computation-caching.md @@ -124,7 +124,7 @@ If the outputs property is missing, Nx defaults to caching the appropriate folde By default, Nx uses a local computation cache. **Because the word "cache" appears in the description, the phrase "artifact caching" comes to mind. But this isn't the right way to think about it. What Nx does is really computation memoization.** Nx doesn't choose to use or not use the cached value. There are no versions. It is transparent: Nx skips the computation only when running the computation would have produced the same result. -Nx stores the cached values only for a week, after which they are deleted. To clear the cache, delete the [cache directory](customizing-the-cache-location), and Nx creates a new one the next time it tries to access it. +Nx stores the cached values only for a week, after which they are deleted. To clear the cache, delete the [cache directory](#customizing-the-cache-location), and Nx creates a new one the next time it tries to access it. ## Distributed Computation Caching