miel.truyen/nx
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

docs(core): update link to nrwl/nx-incremental-large-repo (#16862)

Browse Source
This commit is contained in:
Richard Roozenboom 2023-05-08 15:25:55 +02:00 committed by GitHub
parent 0654776106
commit ceabe46e89
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/shared/incremental-builds.md
View File

@ -35,9 +35,9 @@ In an incremental build scenario, when building the app, all it's dependencies n
It is costly to rebuild all the buildable libraries from scratch every time you want to serve the app. That's why the Nx computation caching is so important. The caching allows us to only rebuild a small subset of the libraries, which results in much better performance. It is costly to rebuild all the buildable libraries from scratch every time you want to serve the app. That's why the Nx computation caching is so important. The caching allows us to only rebuild a small subset of the libraries, which results in much better performance.
If we can share the cache with our teammates, we can get a much better dev experience. For instance, [this repo](https://github.com/nx/nx-incremental-large-repo) has a large application, where `nx serve` takes just a few seconds. If we can share the cache with our teammates, we can get a much better dev experience. For instance, [this repo](https://github.com/nrwl/nx-incremental-large-repo) has a large application, where `nx serve` takes just a few seconds.
{% github-repository url="https://github.com/nx/nx-incremental-large-repo" /%} {% github-repository url="https://github.com/nrwl/nx-incremental-large-repo" /%}
![comparison: webpack vs incremental build](/shared/incremental-build-webpack-vs-incremental.png) ![comparison: webpack vs incremental build](/shared/incremental-build-webpack-vs-incremental.png)