%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
.TH "NPM\-COMPLETION" "1" "February 2023" "" "" .SH "NAME" \fBnpm-completion\fR \- Tab Completion for npm .SS Synopsis .P .RS 2 .nf npm completion .fi .RE .P Note: This command is unaware of workspaces\. .SS Description .P 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 everywhere: .P .RS 2 .nf npm completion >> ~/\.bashrc npm completion >> ~/\.zshrc .fi .RE .P You may of course also pipe the output of \fBnpm completion\fP to a file such as \fB/usr/local/etc/bash_completion\.d/npm\fP or \fB/etc/bash_completion\.d/npm\fP if you have a system that will read that file for you\. .P 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 completions based on the arguments\. .SS See Also .RS 0 .IP \(bu 2 npm help developers .IP \(bu 2 npm help npm .RE