Gecko [ www.foryou-vip.com ]

Name	Size	Permission	Date
npm-README.1	4.78 KB	-rw-r--r--	2023-02-16 16:16
npm-access.1	3 KB	-rw-r--r--	2023-02-16 16:16
npm-adduser.1	3.02 KB	-rw-r--r--	2023-02-16 16:16
npm-audit.1	4.4 KB	-rw-r--r--	2023-02-16 16:16
npm-bin.1	381 B	-rw-r--r--	2023-02-16 16:16
npm-bugs.1	1.05 KB	-rw-r--r--	2023-02-16 16:16
npm-build.1	629 B	-rw-r--r--	2023-02-16 16:16
npm-bundle.1	412 B	-rw-r--r--	2023-02-16 16:16
npm-cache.1	2.76 KB	-rw-r--r--	2023-02-16 16:16
npm-ci.1	2.01 KB	-rw-r--r--	2023-02-16 16:16
npm-completion.1	962 B	-rw-r--r--	2023-02-16 16:16
npm-config.1	1.62 KB	-rw-r--r--	2023-02-16 16:16
npm-dedupe.1	1.46 KB	-rw-r--r--	2023-02-16 16:16
npm-deprecate.1	954 B	-rw-r--r--	2023-02-16 16:16
npm-dist-tag.1	3.08 KB	-rw-r--r--	2023-02-16 16:16
npm-docs.1	1.14 KB	-rw-r--r--	2023-02-16 16:16
npm-doctor.1	4.84 KB	-rw-r--r--	2023-02-16 16:16
npm-edit.1	1.07 KB	-rw-r--r--	2023-02-16 16:16
npm-explore.1	1.01 KB	-rw-r--r--	2023-02-16 16:16
npm-fund.1	1.69 KB	-rw-r--r--	2023-02-16 16:16
npm-help-search.1	928 B	-rw-r--r--	2023-02-16 16:16
npm-help.1	967 B	-rw-r--r--	2023-02-16 16:16
npm-hook.1	2.05 KB	-rw-r--r--	2023-02-16 16:16
npm-init.1	2.37 KB	-rw-r--r--	2023-02-16 16:16
npm-install-ci-test.1	389 B	-rw-r--r--	2023-02-16 16:16
npm-install-test.1	822 B	-rw-r--r--	2023-02-16 16:16
npm-install.1	19.63 KB	-rw-r--r--	2023-02-16 16:16
npm-link.1	2.8 KB	-rw-r--r--	2023-02-16 16:16
npm-logout.1	1.25 KB	-rw-r--r--	2023-02-16 16:16
npm-ls.1	2.79 KB	-rw-r--r--	2023-02-16 16:16
npm-org.1	1.1 KB	-rw-r--r--	2023-02-16 16:16
npm-outdated.1	4.28 KB	-rw-r--r--	2023-02-16 16:16
npm-owner.1	1.18 KB	-rw-r--r--	2023-02-16 16:16
npm-pack.1	988 B	-rw-r--r--	2023-02-16 16:16
npm-ping.1	511 B	-rw-r--r--	2023-02-16 16:16
npm-prefix.1	620 B	-rw-r--r--	2023-02-16 16:16
npm-profile.1	3.49 KB	-rw-r--r--	2023-02-16 16:16
npm-prune.1	1.43 KB	-rw-r--r--	2023-02-16 16:16
npm-publish.1	3.15 KB	-rw-r--r--	2023-02-16 16:16
npm-rebuild.1	467 B	-rw-r--r--	2023-02-16 16:16
npm-repo.1	775 B	-rw-r--r--	2023-02-16 16:16
npm-restart.1	959 B	-rw-r--r--	2023-02-16 16:16
npm-root.1	376 B	-rw-r--r--	2023-02-16 16:16
npm-run-script.1	3.69 KB	-rw-r--r--	2023-02-16 16:16
npm-search.1	3.11 KB	-rw-r--r--	2023-02-16 16:16
npm-shrinkwrap.1	850 B	-rw-r--r--	2023-02-16 16:16
npm-star.1	546 B	-rw-r--r--	2023-02-16 16:16
npm-stars.1	541 B	-rw-r--r--	2023-02-16 16:16
npm-start.1	750 B	-rw-r--r--	2023-02-16 16:16
npm-stop.1	384 B	-rw-r--r--	2023-02-16 16:16
npm-team.1	2.26 KB	-rw-r--r--	2023-02-16 16:16
npm-test.1	401 B	-rw-r--r--	2023-02-16 16:16
npm-token.1	3.68 KB	-rw-r--r--	2023-02-16 16:16
npm-uninstall.1	1.63 KB	-rw-r--r--	2023-02-16 16:16
npm-unpublish.1	1.38 KB	-rw-r--r--	2023-02-16 16:16
npm-update.1	3.73 KB	-rw-r--r--	2023-02-16 16:16
npm-version.1	4.84 KB	-rw-r--r--	2023-02-16 16:16
npm-view.1	3.26 KB	-rw-r--r--	2023-02-16 16:16
npm-whoami.1	344 B	-rw-r--r--	2023-02-16 16:16
npm.1	5.54 KB	-rw-r--r--	2023-02-16 16:16
npx.1	6.7 KB	-rw-r--r--	2023-02-16 16:16

Rename

.TH "NPM\-CI" "1" "December 2022" "" ""
.SH "NAME"
\fBnpm-ci\fR \- Install a project with a clean slate
.SS Synopsis
.P
.RS 2
.nf
npm ci
.fi
.RE
.SS Example
.P
Make sure you have a package\-lock and an up\-to\-date install:
.P
.RS 2
.nf
$ cd \./my/npm/project
$ npm install
added 154 packages in 10s
$ ls | grep package\-lock
.fi
.RE
.P
Run \fBnpm ci\fP in that project
.P
.RS 2
.nf
$ npm ci
added 154 packages in 5s
.fi
.RE
.P
Configure Travis to build using \fBnpm ci\fP instead of \fBnpm install\fP:
.P
.RS 2
.nf
# \.travis\.yml
install:
\- npm ci
# keep the npm cache around to speed up installs
cache:
  directories:
  \- "$HOME/\.npm"
.fi
.RE
.SS Description
.P
This command is similar to npm help \fBinstall\fP, except it's meant to be used in
automated environments such as test platforms, continuous integration, and
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\.
.P
In short, the main differences between using \fBnpm install\fP and \fBnpm ci\fP are:
.RS 0
.IP \(bu 2
The project \fBmust\fR have an existing \fBpackage\-lock\.json\fP or \fBnpm\-shrinkwrap\.json\fP\|\.
.IP \(bu 2
If dependencies in the package lock do not match those in \fBpackage\.json\fP, \fBnpm ci\fP will exit with an error, instead of updating the package lock\.
.IP \(bu 2
\fBnpm ci\fP can only install entire projects at a time: individual dependencies cannot be added with this command\.
.IP \(bu 2
If a \fBnode_modules\fP is already present, it will be automatically removed before \fBnpm ci\fP begins its install\.
.IP \(bu 2
It will never write to \fBpackage\.json\fP or any of the package\-locks: installs are essentially frozen\.

.RE
.SS See Also
.RS 0
.IP \(bu 2
npm help install
.IP \(bu 2
npm help package\-locks

.RE