2017-05-10 05:46:02 +08:00
|
|
|
.TH "NPM\-COMPLETION" "1" "May 2017" "" ""
|
2011-11-27 01:21:03 +08:00
|
|
|
.SH "NAME"
|
2014-09-25 05:41:07 +08:00
|
|
|
\fBnpm-completion\fR \- Tab Completion for npm
|
|
|
|
|
.SH SYNOPSIS
|
|
|
|
|
.P
|
|
|
|
|
.RS 2
|
2014-11-05 07:08:12 +08:00
|
|
|
.nf
|
2015-10-10 14:13:57 +08:00
|
|
|
source <(npm completion)
|
2014-11-05 07:08:12 +08:00
|
|
|
.fi
|
2014-09-25 05:41:07 +08:00
|
|
|
.RE
|
|
|
|
|
.SH DESCRIPTION
|
|
|
|
|
.P
|
2011-11-27 01:21:03 +08:00
|
|
|
Enables tab\-completion in all npm commands\.
|
|
|
|
|
.P
|
|
|
|
|
The synopsis above
|
|
|
|
|
loads the completions into your current shell\. Adding it to
|
|
|
|
|
your ~/\.bashrc or ~/\.zshrc will make the completions available
|
2015-10-10 14:13:57 +08:00
|
|
|
everywhere:
|
|
|
|
|
.P
|
|
|
|
|
.RS 2
|
|
|
|
|
.nf
|
|
|
|
|
npm completion >> ~/\.bashrc
|
|
|
|
|
npm completion >> ~/\.zshrc
|
|
|
|
|
.fi
|
|
|
|
|
.RE
|
2011-11-27 01:21:03 +08:00
|
|
|
.P
|
|
|
|
|
You may of course also pipe the output of npm completion to a file
|
2015-07-25 06:09:52 +08:00
|
|
|
such as \fB/usr/local/etc/bash_completion\.d/npm\fP if you have a system
|
2011-11-27 01:21:03 +08:00
|
|
|
that will read that file for you\.
|
|
|
|
|
.P
|
2015-07-25 06:09:52 +08:00
|
|
|
When \fBCOMP_CWORD\fP, \fBCOMP_LINE\fP, and \fBCOMP_POINT\fP are defined in the
|
|
|
|
|
environment, \fBnpm completion\fP acts in "plumbing mode", and outputs
|
2011-11-27 01:21:03 +08:00
|
|
|
completions based on the arguments\.
|
2014-09-25 05:41:07 +08:00
|
|
|
.SH SEE ALSO
|
|
|
|
|
.RS 0
|
|
|
|
|
.IP \(bu 2
|
2014-09-17 06:38:50 +08:00
|
|
|
npm help 7 developers
|
2014-09-25 05:41:07 +08:00
|
|
|
.IP \(bu 2
|
2011-11-27 01:21:03 +08:00
|
|
|
npm help npm
|
2014-09-25 05:41:07 +08:00
|
|
|
|
|
|
|
|
.RE
|
2011-11-27 01:21:03 +08:00
|
|
|
|
