nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-10-28 03:25:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1224 from no-yan/chore/fix-typo

Browse Source
This commit is contained in:
Raz Luvaton
2023-03-19 14:12:58 +02:00
committed by GitHub
parent 4b1cd95d18 e546e18c34
commit 24b6e6976e
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
sections/docker/clean-cache.french.md
View File

@ -6,7 +6,7 @@
Node package managers, npm & Yarn, cache the installed packages locally so that future projects which need the same libraries won't need to fetch from a remote repository. Although this duplicates the packages and consumes more storage - it pays off in a local development environment that typically keeps installing the same packages. In a Docker container this storage increase is worthless since it installs the dependency only once. By removing this cache, using a single line of code, tens of MB are shaved from the image. While doing so, ensure that it doesn't exit with non-zero code and fail the CI build because of caching issues - This can be avoided by including the --force flag.
*Please not that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*
*Please note that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*
<br/><br/>

2
sections/docker/clean-cache.md
View File

@ -6,7 +6,7 @@
Node package managers, npm & Yarn, cache the installed packages locally so that future projects which need the same libraries won't need to fetch from a remote repository. Although this duplicates the packages and consumes more storage - it pays off in a local development environment that typically keeps installing the same packages. In a Docker container this storage increase is worthless since it installs the dependency only once. By removing this cache, using a single line of code, tens of MB are shaved from the image. While doing so, ensure that it doesn't exit with non-zero code and fail the CI build because of caching issues - This can be avoided by including the --force flag.
*Please not that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*
*Please note that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*
<br/><br/>