diff options
| author | Kat Marchán <kzm@zkat.tech> | 2018-08-29 21:41:56 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-08-29 21:41:56 +0300 |
| commit | fc1a8d185fc678cdf3784d9df9eef9094e0b2dec (patch) | |
| tree | 02400c67b41fa86520a9c6a805a08929dc4d316d /doc | |
| parent | 414f2d1a1bdffc02ed31ebb48a43216f284c21d4 (diff) | |
ci: backronym ci to clean-install (#57)
Credit: @zkat
Reviewed-By: @jefflembeck
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/cli/npm-ci.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/cli/npm-ci.md b/doc/cli/npm-ci.md index b1406e36a..289bb7c19 100644 --- a/doc/cli/npm-ci.md +++ b/doc/cli/npm-ci.md @@ -39,9 +39,10 @@ cache: This command is similar to `npm-install(1)`, except it's meant to be used in automated environments such as test platforms, continuous integration, and -deployment. It can be significantly faster than a regular npm install by -skipping certain user-oriented features. It is also more strict than a regular -install, which can help catch errors or inconsistencies caused by the +deployment -- or any situation where you want to make sure you're doing a clean +install of your dependencies. It can be significantly faster than a regular npm +install by skipping certain user-oriented features. It is also more strict than +a regular install, which can help catch errors or inconsistencies caused by the incrementally-installed local environments of most npm users. In short, the main differences between using `npm install` and `npm ci` are: |