mirror of https://github.com/lukechilds/node.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
30 lines
741 B
30 lines
741 B
13 years ago
|
npm-completion(1) -- Tab Completion for npm
|
||
|
|
===========================================
|
||
|
|
|
||
|
|
## SYNOPSIS
|
||
|
|
|
||
|
|
. <(npm completion)
|
||
|
|
|
||
|
|
## DESCRIPTION
|
||
|
|
|
||
|
|
Enables tab-completion in all npm commands.
|
||
|
|
|
||
|
|
The synopsis above
|
||
|
|
loads the completions into your current shell. Adding it to
|
||
|
|
your ~/.bashrc or ~/.zshrc will make the completions available
|
||
|
|
everywhere.
|
||
|
|
|
||
|
|
You may of course also pipe the output of npm completion to a file
|
||
|
|
such as `/usr/local/etc/bash_completion.d/npm` if you have a system
|
||
|
|
that will read that file for you.
|
||
|
|
|
||
|
|
When `COMP_CWORD`, `COMP_LINE`, and `COMP_POINT` are defined in the
|
||
|
|
environment, `npm completion` acts in "plumbing mode", and outputs
|
||
|
|
completions based on the arguments.
|
||
|
|
|
||
|
|
## SEE ALSO
|
||
|
|
|
||
|
|
* npm-developers(1)
|
||
|
|
* npm-faq(1)
|
||
|
|
* npm(1)
|