Skip to content

Commit

Permalink
docs(core): update broken link; wrap nx-dev serve command with npx so…
Browse files Browse the repository at this point in the history
… ts-node does not need to be available globally (#7030)
  • Loading branch information
jaysoo committed Sep 16, 2021
1 parent e18c0a0 commit f4bc240
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion docs/shared/computation-caching.md
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion nx-dev/nx-dev/project.json
Expand Up @@ -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
Expand Down
Expand Up @@ -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

Expand Down

1 comment on commit f4bc240

@vercel
Copy link

@vercel vercel bot commented on f4bc240 Sep 16, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please sign in to comment.