diff options
Diffstat (limited to 'deps/npm/man/man1')
42 files changed, 363 insertions, 363 deletions
diff --git a/deps/npm/man/man1/npm-README.1 b/deps/npm/man/man1/npm-README.1 index 8235f7ccfe..997fa50f29 100644 --- a/deps/npm/man/man1/npm-README.1 +++ b/deps/npm/man/man1/npm-README.1 @@ -7,7 +7,7 @@ Build Status \fIhttps://img\.shields\.io/travis/npm/npm/master\.svg\fR \fIhttps: .P This is just enough info to get you up and running\. .P -Much more info available via \fBnpm help\fR once it's installed\. +Much more info available via \fBnpm help\fP once it's installed\. .SH IMPORTANT .P \fBYou need node v0\.8 or higher to run this program\.\fR @@ -25,7 +25,7 @@ Get the MSI \fIhttp://nodejs\.org/download/\fR\|\. npm is in it\. Get the pkg \fIhttp://nodejs\.org/download/\fR\|\. npm is in it\. .SS Other Sorts of Unices .P -Run \fBmake install\fR\|\. npm will be installed with node\. +Run \fBmake install\fP\|\. npm will be installed with node\. .P If you want a more fancy pants install (a different version, customized paths, etc\.) then read on\. @@ -60,17 +60,17 @@ npm_debug=1 sh install\.sh .RE .SS Even Fancier .P -Get the code with git\. Use \fBmake\fR to build the docs and do other stuff\. -If you plan on hacking on npm, \fBmake link\fR is your friend\. +Get the code with git\. Use \fBmake\fP to build the docs and do other stuff\. +If you plan on hacking on npm, \fBmake link\fP is your friend\. .P If you've got the npm source code, you can also semi\-permanently set -arbitrary config keys using the \fB\|\./configure \-\-key=val \.\.\.\fR, and then -run npm commands by doing \fBnode cli\.js <cmd> <args>\fR\|\. (This is helpful +arbitrary config keys using the \fB\|\./configure \-\-key=val \.\.\.\fP, and then +run npm commands by doing \fBnode cli\.js <cmd> <args>\fP\|\. (This is helpful for testing, or running stuff without actually installing npm itself\.) .SH Windows Install or Upgrade .P You can download a zip file from https://github\.com/npm/npm/releases, and -unpack it in the \fBnode_modules\\npm\\\fR folder inside node's installation folder\. +unpack it in the \fBnode_modules\\npm\\\fP folder inside node's installation folder\. .P To upgrade to npm 2, follow the Windows upgrade instructions in the npm Troubleshooting Guide: @@ -105,11 +105,11 @@ Usually, the above instructions are sufficient\. That will remove npm, but leave behind anything you've installed\. .P If you would like to remove all the packages that you have installed, -then you can use the \fBnpm ls\fR command to find them, and then \fBnpm rm\fR to +then you can use the \fBnpm ls\fP command to find them, and then \fBnpm rm\fP to remove them\. .P To remove cruft left behind by npm 0\.x, you can use the included -\fBclean\-old\.sh\fR script file\. You can run it conveniently like this: +\fBclean\-old\.sh\fP script file\. You can run it conveniently like this: .P .RS 2 .nf @@ -136,7 +136,7 @@ you have chosen\. Although npm can be used programmatically, its API is meant for use by the CLI \fIonly\fR, and no guarantees are made regarding its fitness for any other purpose\. If you want to use npm to reliably perform some task, the safest thing to do is -to invoke the desired \fBnpm\fR command with appropriate arguments\. +to invoke the desired \fBnpm\fP command with appropriate arguments\. .P The semantic version of npm refers to the CLI itself, rather than the underlying API\. \fIThe internal API is not guaranteed to remain stable even when @@ -165,25 +165,25 @@ npm\.load(myConfigObject, function (er) { .fi .RE .P -The \fBload\fR function takes an object hash of the command\-line configs\. -The various \fBnpm\.commands\.<cmd>\fR functions take an \fBarray\fR of +The \fBload\fP function takes an object hash of the command\-line configs\. +The various \fBnpm\.commands\.<cmd>\fP functions take an \fBarray\fR of positional argument \fBstrings\fR\|\. The last argument to any -\fBnpm\.commands\.<cmd>\fR function is a callback\. Some commands take other +\fBnpm\.commands\.<cmd>\fP function is a callback\. Some commands take other optional arguments\. Read the source\. .P You cannot set configs individually for any single npm function at this -time\. Since \fBnpm\fR is a singleton, any call to \fBnpm\.config\.set\fR will +time\. Since \fBnpm\fP is a singleton, any call to \fBnpm\.config\.set\fP will change the value for \fIall\fR npm commands in that process\. .P -See \fB\|\./bin/npm\-cli\.js\fR for an example of pulling config values off of the +See \fB\|\./bin/npm\-cli\.js\fP for an example of pulling config values off of the command line arguments using nopt\. You may also want to check out \fBnpm -help config\fR to learn about all the options you can set there\. +help config\fP to learn about all the options you can set there\. .SH More Docs .P Check out the docs \fIhttps://docs\.npmjs\.com/\fR, especially the faq \fIhttps://docs\.npmjs\.com/misc/faq\fR\|\. .P -You can use the \fBnpm help\fR command to read any of them\. +You can use the \fBnpm help\fP command to read any of them\. .P If you're a developer, and you want to use npm to publish your program, you should read this \fIhttps://docs\.npmjs\.com/misc/developers\fR @@ -237,7 +237,7 @@ https://github\.com/npm/npm/issues .RE .P Be sure to include \fIall\fR of the output from the npm command that didn't work -as expected\. The \fBnpm\-debug\.log\fR file is also helpful to provide\. +as expected\. The \fBnpm\-debug\.log\fP file is also helpful to provide\. .P You can also look for isaacs in #node\.js on irc://irc\.freenode\.net\. He will no doubt tell you to put the output in a gist or email\. diff --git a/deps/npm/man/man1/npm-access.1 b/deps/npm/man/man1/npm-access.1 index e99a216d02..f1d7272469 100644 --- a/deps/npm/man/man1/npm-access.1 +++ b/deps/npm/man/man1/npm-access.1 @@ -19,7 +19,7 @@ npm access edit [<package>] .P Used to set access controls on private packages\. .P -For all of the subcommands, \fBnpm access\fR will perform actions on the packages +For all of the subcommands, \fBnpm access\fP will perform actions on the packages in the current working directory if no package name is passed to the subcommand\. .RS 0 @@ -36,19 +36,19 @@ Show all of the access privileges for a package\. Will only show permissions for packages to which you have at least read access\. .IP \(bu 2 edit: -Set the access privileges for a package at once using \fB$EDITOR\fR\|\. +Set the access privileges for a package at once using \fB$EDITOR\fP\|\. .RE .SH DETAILS .P -\fBnpm access\fR always operates directly on the current registry, configurable -from the command line using \fB\-\-registry=<registry url>\fR\|\. +\fBnpm access\fP always operates directly on the current registry, configurable +from the command line using \fB\-\-registry=<registry url>\fP\|\. .P Unscoped packages are \fIalways public\fR\|\. .P Scoped packages \fIdefault to restricted\fR, but you can either publish them as -public using \fBnpm publish \-\-access=public\fR, or set their access as public using -\fBnpm access public\fR after the initial publish\. +public using \fBnpm publish \-\-access=public\fP, or set their access as public using +\fBnpm access public\fP after the initial publish\. .P You must have privileges to set the access of a package: .RS 0 @@ -64,7 +64,7 @@ of a team or directly as an owner\. .P If your account is not paid, then attempts to publish scoped packages will fail with an HTTP 402 status code (logically enough), unless you use -\fB\-\-access=public\fR\|\. +\fB\-\-access=public\fP\|\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-adduser.1 b/deps/npm/man/man1/npm-adduser.1 index 7d00b79527..ade506ef53 100644 --- a/deps/npm/man/man1/npm-adduser.1 +++ b/deps/npm/man/man1/npm-adduser.1 @@ -10,9 +10,9 @@ npm adduser [\-\-registry=url] [\-\-scope=@orgname] [\-\-always\-auth] .RE .SH DESCRIPTION .P -Create or verify a user named \fB<username>\fR in the specified registry, and -save the credentials to the \fB\|\.npmrc\fR file\. If no registry is specified, -the default registry will be used (see npm help 7 \fBnpm\-config\fR)\. +Create or verify a user named \fB<username>\fP in the specified registry, and +save the credentials to the \fB\|\.npmrc\fP file\. If no registry is specified, +the default registry will be used (see npm help 7 \fBnpm\-config\fP)\. .P The username, password, and email are read in from prompts\. .P @@ -25,20 +25,20 @@ authorize on a new machine\. When authenticating on a new machine, the username, password and email address must all match with your existing record\. .P -\fBnpm login\fR is an alias to \fBadduser\fR and behaves exactly the same way\. +\fBnpm login\fP is an alias to \fBadduser\fP and behaves exactly the same way\. .SH CONFIGURATION .SS registry .P Default: http://registry\.npmjs\.org/ .P -The base URL of the npm package registry\. If \fBscope\fR is also specified, -this registry will only be used for packages with that scope\. See npm help 7 \fBnpm\-scope\fR\|\. +The base URL of the npm package registry\. If \fBscope\fP is also specified, +this registry will only be used for packages with that scope\. See npm help 7 \fBnpm\-scope\fP\|\. .SS scope .P Default: none .P If specified, the user and login credentials given will be associated -with the specified scope\. See npm help 7 \fBnpm\-scope\fR\|\. You can use both at the same time, +with the specified scope\. See npm help 7 \fBnpm\-scope\fP\|\. You can use both at the same time, e\.g\. .P .RS 2 @@ -55,7 +55,7 @@ Default: false .P If specified, save configuration indicating that all requests to the given registry should include authorization information\. Useful for private -registries\. Can be used with \fB\-\-registry\fR and / or \fB\-\-scope\fR, e\.g\. +registries\. Can be used with \fB\-\-registry\fP and / or \fB\-\-scope\fP, e\.g\. .P .RS 2 .nf @@ -64,8 +64,8 @@ npm adduser \-\-registry=http://private\-registry\.example\.com \-\-always\-auth .RE .P This will ensure that all requests to that registry (including for tarballs) -include an authorization header\. See \fBalways\-auth\fR in npm help 7 \fBnpm\-config\fR for more -details on always\-auth\. Registry\-specific configuration of \fBalways\-auth\fR takes +include an authorization header\. See \fBalways\-auth\fP in npm help 7 \fBnpm\-config\fP for more +details on always\-auth\. Registry\-specific configuration of \fBalways\-auth\fP takes precedence over any global configuration\. .SH SEE ALSO .RS 0 diff --git a/deps/npm/man/man1/npm-bugs.1 b/deps/npm/man/man1/npm-bugs.1 index 126065fa5c..fde8d06191 100644 --- a/deps/npm/man/man1/npm-bugs.1 +++ b/deps/npm/man/man1/npm-bugs.1 @@ -12,20 +12,20 @@ npm bugs (with no args in a package dir) .SH DESCRIPTION .P This command tries to guess at the likely location of a package's -bug tracker URL, and then tries to open it using the \fB\-\-browser\fR +bug tracker URL, and then tries to open it using the \fB\-\-browser\fP config param\. If no package name is provided, it will search for -a \fBpackage\.json\fR in the current folder and use the \fBname\fR property\. +a \fBpackage\.json\fP in the current folder and use the \fBname\fP property\. .SH CONFIGURATION .SS browser .RS 0 .IP \(bu 2 -Default: OS X: \fB"open"\fR, Windows: \fB"start"\fR, Others: \fB"xdg\-open"\fR +Default: OS X: \fB"open"\fP, Windows: \fB"start"\fP, Others: \fB"xdg\-open"\fP .IP \(bu 2 Type: String .RE .P -The browser that is called by the \fBnpm bugs\fR command to open websites\. +The browser that is called by the \fBnpm bugs\fP command to open websites\. .SS registry .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-build.1 b/deps/npm/man/man1/npm-build.1 index 7bfeb2b84a..d17fe158c8 100644 --- a/deps/npm/man/man1/npm-build.1 +++ b/deps/npm/man/man1/npm-build.1 @@ -10,13 +10,13 @@ npm build <package\-folder> .RE .RS 0 .IP \(bu 2 -\fB<package\-folder>\fR: -A folder containing a \fBpackage\.json\fR file in its root\. +\fB<package\-folder>\fP: +A folder containing a \fBpackage\.json\fP file in its root\. .RE .SH DESCRIPTION .P -This is the plumbing command called by \fBnpm link\fR and \fBnpm install\fR\|\. +This is the plumbing command called by \fBnpm link\fP and \fBnpm install\fP\|\. .P It should generally be called during installation, but if you need to run it directly, run: diff --git a/deps/npm/man/man1/npm-bundle.1 b/deps/npm/man/man1/npm-bundle.1 index 202a09079c..04bd969427 100644 --- a/deps/npm/man/man1/npm-bundle.1 +++ b/deps/npm/man/man1/npm-bundle.1 @@ -3,11 +3,11 @@ \fBnpm-bundle\fR \- REMOVED .SH DESCRIPTION .P -The \fBnpm bundle\fR command has been removed in 1\.0, for the simple reason +The \fBnpm bundle\fP command has been removed in 1\.0, for the simple reason that it is no longer necessary, as the default behavior is now to install packages into the local space\. .P -Just use \fBnpm install\fR now to do what \fBnpm bundle\fR used to do\. +Just use \fBnpm install\fP now to do what \fBnpm bundle\fP used to do\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-cache.1 b/deps/npm/man/man1/npm-cache.1 index dd473fc216..5c84c222a6 100644 --- a/deps/npm/man/man1/npm-cache.1 +++ b/deps/npm/man/man1/npm-cache.1 @@ -27,8 +27,8 @@ add data to the local installation cache explicitly\. .IP \(bu 2 ls: Show the data in the cache\. Argument is a path to show in the cache -folder\. Works a bit like the \fBfind\fR program, but limited by the -\fBdepth\fR config\. +folder\. Works a bit like the \fBfind\fP program, but limited by the +\fBdepth\fP config\. .IP \(bu 2 clean: Delete data out of the cache folder\. If an argument is provided, then @@ -38,9 +38,9 @@ the entire cache is cleared\. .RE .SH DETAILS .P -npm stores cache data in the directory specified in \fBnpm config get cache\fR\|\. +npm stores cache data in the directory specified in \fBnpm config get cache\fP\|\. For each package that is added to the cache, three pieces of information are -stored in \fB{cache}/{name}/{version}\fR: +stored in \fB{cache}/{name}/{version}\fP: .RS 0 .IP \(bu 2 \|\.\.\./package/package\.json: @@ -51,18 +51,18 @@ The tarball for that version\. .RE .P -Additionally, whenever a registry request is made, a \fB\|\.cache\.json\fR file +Additionally, whenever a registry request is made, a \fB\|\.cache\.json\fP file is placed at the corresponding URI, to store the ETag and the requested -data\. This is stored in \fB{cache}/{hostname}/{path}/\.cache\.json\fR\|\. +data\. This is stored in \fB{cache}/{hostname}/{path}/\.cache\.json\fP\|\. .P -Commands that make non\-essential registry requests (such as \fBsearch\fR and -\fBview\fR, or the completion scripts) generally specify a minimum timeout\. -If the \fB\|\.cache\.json\fR file is younger than the specified timeout, then +Commands that make non\-essential registry requests (such as \fBsearch\fP and +\fBview\fP, or the completion scripts) generally specify a minimum timeout\. +If the \fB\|\.cache\.json\fP file is younger than the specified timeout, then they do not make an HTTP request to the registry\. .SH CONFIGURATION .SS cache .P -Default: \fB~/\.npm\fR on Posix, or \fB%AppData%/npm\-cache\fR on Windows\. +Default: \fB~/\.npm\fP on Posix, or \fB%AppData%/npm\-cache\fP on Windows\. .P The root cache folder\. .SH SEE ALSO diff --git a/deps/npm/man/man1/npm-completion.1 b/deps/npm/man/man1/npm-completion.1 index 13a7135e08..15a8a21a0d 100644 --- a/deps/npm/man/man1/npm-completion.1 +++ b/deps/npm/man/man1/npm-completion.1 @@ -18,11 +18,11 @@ your ~/\.bashrc or ~/\.zshrc will make the completions available everywhere\. .P You may of course also pipe the output of npm completion to a file -such as \fB/usr/local/etc/bash_completion\.d/npm\fR if you have a system +such as \fB/usr/local/etc/bash_completion\.d/npm\fP if you have a system that will read that file for you\. .P -When \fBCOMP_CWORD\fR, \fBCOMP_LINE\fR, and \fBCOMP_POINT\fR are defined in the -environment, \fBnpm completion\fR acts in "plumbing mode", and outputs +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\. .SH SEE ALSO .RS 0 diff --git a/deps/npm/man/man1/npm-config.1 b/deps/npm/man/man1/npm-config.1 index fddf9dfa9e..75c458ddbd 100644 --- a/deps/npm/man/man1/npm-config.1 +++ b/deps/npm/man/man1/npm-config.1 @@ -18,14 +18,14 @@ npm set <key> <value> [\-\-global] .SH DESCRIPTION .P npm gets its config settings from the command line, environment -variables, \fBnpmrc\fR files, and in some cases, the \fBpackage\.json\fR file\. +variables, \fBnpmrc\fP files, and in some cases, the \fBpackage\.json\fP file\. .P See npm help 5 npmrc for more information about the npmrc files\. .P -See npm help 7 \fBnpm\-config\fR for a more thorough discussion of the mechanisms +See npm help 7 \fBnpm\-config\fP for a more thorough discussion of the mechanisms involved\. .P -The \fBnpm config\fR command can be used to update and edit the contents +The \fBnpm config\fP command can be used to update and edit the contents of the user and global npmrc files\. .SH Sub\-commands .P @@ -76,7 +76,7 @@ npm config edit .fi .RE .P -Opens the config file in an editor\. Use the \fB\-\-global\fR flag to edit the +Opens the config file in an editor\. Use the \fB\-\-global\fP flag to edit the global config\. .SH SEE ALSO .RS 0 diff --git a/deps/npm/man/man1/npm-dedupe.1 b/deps/npm/man/man1/npm-dedupe.1 index ac96395296..587cfb7ac5 100644 --- a/deps/npm/man/man1/npm-dedupe.1 +++ b/deps/npm/man/man1/npm-dedupe.1 @@ -27,7 +27,7 @@ a .fi .RE .P -In this case, npm help \fBnpm\-dedupe\fR will transform the tree to: +In this case, npm help \fBnpm\-dedupe\fP will transform the tree to: .P .RS 2 .nf @@ -58,7 +58,7 @@ registry\. .P This feature is experimental, and may change in future versions\. .P -The \fB\-\-tag\fR argument will apply to all of the affected dependencies\. If a +The \fB\-\-tag\fP argument will apply to all of the affected dependencies\. If a tag with the given name exists, the tagged version is preferred over newer versions\. .SH SEE ALSO diff --git a/deps/npm/man/man1/npm-deprecate.1 b/deps/npm/man/man1/npm-deprecate.1 index a379e6b133..ae01b145a4 100644 --- a/deps/npm/man/man1/npm-deprecate.1 +++ b/deps/npm/man/man1/npm-deprecate.1 @@ -23,9 +23,9 @@ npm deprecate my\-thing@"< 0\.2\.3" "critical bug fixed in v0\.2\.3" .RE .P Note that you must be the package owner to deprecate something\. See the -\fBowner\fR and \fBadduser\fR help topics\. +\fBowner\fP and \fBadduser\fP help topics\. .P -To un\-deprecate a package, specify an empty string (\fB""\fR) for the \fBmessage\fR argument\. +To un\-deprecate a package, specify an empty string (\fB""\fP) for the \fBmessage\fP argument\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-dist-tag.1 b/deps/npm/man/man1/npm-dist-tag.1 index b821da4f9e..51444feee3 100644 --- a/deps/npm/man/man1/npm-dist-tag.1 +++ b/deps/npm/man/man1/npm-dist-tag.1 @@ -17,7 +17,7 @@ Add, remove, and enumerate distribution tags on a package: .IP \(bu 2 add: Tags the specified version of the package with the specified tag, or the -\fB\-\-tag\fR config if not specified\. +\fB\-\-tag\fP config if not specified\. .IP \(bu 2 rm: Clear a tag that is no longer in use from the package\. @@ -45,32 +45,32 @@ npm install \-\-tag <tag> .fi .RE .P -This also applies to \fBnpm dedupe\fR\|\. +This also applies to \fBnpm dedupe\fP\|\. .P Publishing a package sets the "latest" tag to the published version unless the -\fB\-\-tag\fR option is used\. For example, \fBnpm publish \-\-tag=beta\fR\|\. +\fB\-\-tag\fP option is used\. For example, \fBnpm publish \-\-tag=beta\fP\|\. .SH PURPOSE .P Tags can be used to provide an alias instead of version numbers\. For -example, \fBnpm\fR currently uses the tag "next" to identify the upcoming +example, \fBnpm\fP currently uses the tag "next" to identify the upcoming version, and the tag "latest" to identify the current version\. .P A project might choose to have multiple streams of development, e\.g\., "stable", "canary"\. .SH CAVEATS .P -This command used to be known as \fBnpm tag\fR, which only created new tags, and so +This command used to be known as \fBnpm tag\fP, which only created new tags, and so had a different syntax\. .P Tags must share a namespace with version numbers, because they are specified in -the same slot: \fBnpm install <pkg>@<version>\fR vs \fBnpm install <pkg>@<tag>\fR\|\. +the same slot: \fBnpm install <pkg>@<version>\fP vs \fBnpm install <pkg>@<tag>\fP\|\. .P Tags that can be interpreted as valid semver ranges will be rejected\. For -example, \fBv1\.4\fR cannot be used as a tag, because it is interpreted by semver as -\fB>=1\.4\.0 <1\.5\.0\fR\|\. See https://github\.com/npm/npm/issues/6082\|\. +example, \fBv1\.4\fP cannot be used as a tag, because it is interpreted by semver as +\fB>=1\.4\.0 <1\.5\.0\fP\|\. See https://github\.com/npm/npm/issues/6082\|\. .P The simplest way to avoid semver problems with tags is to use tags that do not -begin with a number or the letter \fBv\fR\|\. +begin with a number or the letter \fBv\fP\|\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-docs.1 b/deps/npm/man/man1/npm-docs.1 index 36c6e042aa..fa164136c5 100644 --- a/deps/npm/man/man1/npm-docs.1 +++ b/deps/npm/man/man1/npm-docs.1 @@ -14,21 +14,21 @@ npm home (with no args in a package dir) .SH DESCRIPTION .P This command tries to guess at the likely location of a package's -documentation URL, and then tries to open it using the \fB\-\-browser\fR +documentation URL, and then tries to open it using the \fB\-\-browser\fP config param\. You can pass multiple package names at once\. If no -package name is provided, it will search for a \fBpackage\.json\fR in -the current folder and use the \fBname\fR property\. +package name is provided, it will search for a \fBpackage\.json\fP in +the current folder and use the \fBname\fP property\. .SH CONFIGURATION .SS browser .RS 0 .IP \(bu 2 -Default: OS X: \fB"open"\fR, Windows: \fB"start"\fR, Others: \fB"xdg\-open"\fR +Default: OS X: \fB"open"\fP, Windows: \fB"start"\fP, Others: \fB"xdg\-open"\fP .IP \(bu 2 Type: String .RE .P -The browser that is called by the \fBnpm docs\fR command to open websites\. +The browser that is called by the \fBnpm docs\fP command to open websites\. .SS registry .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-edit.1 b/deps/npm/man/man1/npm-edit.1 index 711e8576fb..ac1857bc3d 100644 --- a/deps/npm/man/man1/npm-edit.1 +++ b/deps/npm/man/man1/npm-edit.1 @@ -11,26 +11,26 @@ npm edit <name>[@<version>] .SH DESCRIPTION .P Opens the package folder in the default editor (or whatever you've -configured as the npm \fBeditor\fR config \-\- see npm help 7 \fBnpm\-config\fR\|\.) +configured as the npm \fBeditor\fP config \-\- see npm help 7 \fBnpm\-config\fP\|\.) .P After it has been edited, the package is rebuilt so as to pick up any changes in compiled packages\. .P -For instance, you can do \fBnpm install connect\fR to install connect -into your package, and then \fBnpm edit connect\fR to make a few +For instance, you can do \fBnpm install connect\fP to install connect +into your package, and then \fBnpm edit connect\fP to make a few changes to your locally installed copy\. .SH CONFIGURATION .SS editor .RS 0 .IP \(bu 2 -Default: \fBEDITOR\fR environment variable if set, or \fB"vi"\fR on Posix, -or \fB"notepad"\fR on Windows\. +Default: \fBEDITOR\fP environment variable if set, or \fB"vi"\fP on Posix, +or \fB"notepad"\fP on Windows\. .IP \(bu 2 Type: path .RE .P -The command to run for \fBnpm edit\fR or \fBnpm config edit\fR\|\. +The command to run for \fBnpm edit\fP or \fBnpm config edit\fP\|\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-explore.1 b/deps/npm/man/man1/npm-explore.1 index 70786382a7..40d02a1c87 100644 --- a/deps/npm/man/man1/npm-explore.1 +++ b/deps/npm/man/man1/npm-explore.1 @@ -16,7 +16,7 @@ If a command is specified, then it is run in the subshell, which then immediately terminates\. .P This is particularly handy in the case of git submodules in the -\fBnode_modules\fR folder: +\fBnode_modules\fP folder: .P .RS 2 .nf @@ -25,7 +25,7 @@ npm explore some\-dependency \-\- git pull origin master .RE .P Note that the package is \fInot\fR automatically rebuilt afterwards, so be -sure to use \fBnpm rebuild <pkg>\fR if you make any changes\. +sure to use \fBnpm rebuild <pkg>\fP if you make any changes\. .SH CONFIGURATION .SS shell .RS 0 @@ -37,7 +37,7 @@ Type: path .RE .P -The shell to run for the \fBnpm explore\fR command\. +The shell to run for the \fBnpm explore\fP command\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-help-search.1 b/deps/npm/man/man1/npm-help-search.1 index e9284f79d1..08d9443044 100644 --- a/deps/npm/man/man1/npm-help-search.1 +++ b/deps/npm/man/man1/npm-help-search.1 @@ -15,8 +15,8 @@ terms provided, and then list the results, sorted by relevance\. .P If only one result is found, then it will show that help topic\. .P -If the argument to \fBnpm help\fR is not a known help topic, then it will -call \fBhelp\-search\fR\|\. It is rarely if ever necessary to call this +If the argument to \fBnpm help\fP is not a known help topic, then it will +call \fBhelp\-search\fP\|\. It is rarely if ever necessary to call this command directly\. .SH CONFIGURATION .SS long diff --git a/deps/npm/man/man1/npm-help.1 b/deps/npm/man/man1/npm-help.1 index 69a3f9b515..2a529a5d7e 100644 --- a/deps/npm/man/man1/npm-help.1 +++ b/deps/npm/man/man1/npm-help.1 @@ -14,8 +14,8 @@ npm help some search terms If supplied a topic, then show the appropriate documentation page\. .P If the topic does not exist, or if multiple terms are provided, then run -the \fBhelp\-search\fR command to find a match\. Note that, if \fBhelp\-search\fR -finds a single subject, then it will run \fBhelp\fR on that topic, so unique +the \fBhelp\-search\fP command to find a match\. Note that, if \fBhelp\-search\fP +finds a single subject, then it will run \fBhelp\fP on that topic, so unique matches are equivalent to specifying a topic name\. .SH CONFIGURATION .SS viewer @@ -29,7 +29,7 @@ Type: path .P The program to use to view help content\. .P -Set to \fB"browser"\fR to view html help content in the default web browser\. +Set to \fB"browser"\fP to view html help content in the default web browser\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-init.1 b/deps/npm/man/man1/npm-init.1 index f40cd2ce62..d8886630f9 100644 --- a/deps/npm/man/man1/npm-init.1 +++ b/deps/npm/man/man1/npm-init.1 @@ -21,7 +21,7 @@ the options in there\. It is strictly additive, so it does not delete options from your package\.json without a really good reason to do so\. .P -If you invoke it with \fB\-f\fR, \fB\-\-force\fR, \fB\-y\fR, or \fB\-\-yes\fR, it will use only +If you invoke it with \fB\-f\fP, \fB\-\-force\fP, \fB\-y\fP, or \fB\-\-yes\fP, it will use only defaults and not prompt you for any options\. .SH CONFIGURATION .SS scope diff --git a/deps/npm/man/man1/npm-install.1 b/deps/npm/man/man1/npm-install.1 index 994000c8e0..6639b69926 100644 --- a/deps/npm/man/man1/npm-install.1 +++ b/deps/npm/man/man1/npm-install.1 @@ -22,7 +22,7 @@ This command installs a package, and any packages that it depends on\. If the package has a shrinkwrap file, the installation of dependencies will be driven by that\. See npm help shrinkwrap\. .P -A \fBpackage\fR is: +A \fBpackage\fP is: .RS 0 .IP \(bu 2 a) a folder containing a program described by a package\.json file @@ -31,13 +31,13 @@ b) a gzipped tarball containing (a) .IP \(bu 2 c) a url that resolves to (b) .IP \(bu 2 -d) a \fB<name>@<version>\fR that is published on the registry (see npm help 7 \fBnpm\-registry\fR) with (c) +d) a \fB<name>@<version>\fP that is published on the registry (see npm help 7 \fBnpm\-registry\fP) with (c) .IP \(bu 2 -e) a \fB<name>@<tag>\fR that points to (d) +e) a \fB<name>@<tag>\fP that points to (d) .IP \(bu 2 -f) a \fB<name>\fR that has a "latest" tag satisfying (e) +f) a \fB<name>\fP that has a "latest" tag satisfying (e) .IP \(bu 2 -g) a \fB<git remote url>\fR that resolves to (b) +g) a \fB<git remote url>\fP that resolves to (b) .RE .P @@ -47,23 +47,23 @@ perhaps if you also want to be able to easily install it elsewhere after packing it up into a tarball (b)\. .RS 0 .IP \(bu 2 -\fBnpm install\fR (in package directory, no arguments): +\fBnpm install\fP (in package directory, no arguments): Install the dependencies in the local node_modules folder\. - In global mode (ie, with \fB\-g\fR or \fB\-\-global\fR appended to the command), + In global mode (ie, with \fB\-g\fP or \fB\-\-global\fP appended to the command), it installs the current package context (ie, the current working directory) as a global package\. - By default, \fBnpm install\fR will install all modules listed as dependencies\. - With the \fB\-\-production\fR flag (or when the \fBNODE_ENV\fR environment variable - is set to \fBproduction\fR), npm will not install modules listed in - \fBdevDependencies\fR\|\. + By default, \fBnpm install\fP will install all modules listed as dependencies\. + With the \fB\-\-production\fP flag (or when the \fBNODE_ENV\fP environment variable + is set to \fBproduction\fP), npm will not install modules listed in + \fBdevDependencies\fP\|\. .IP \(bu 2 -\fBnpm install <folder>\fR: +\fBnpm install <folder>\fP: Install a package that is sitting in a folder on the filesystem\. .IP \(bu 2 -\fBnpm install <tarball file>\fR: +\fBnpm install <tarball file>\fP: Install a package that is sitting on the filesystem\. Note: if you just want to link a dev directory into your npm root, you can do this more easily by - using \fBnpm link\fR\|\. + using \fBnpm link\fP\|\. Example: .P .RS 2 @@ -72,7 +72,7 @@ after packing it up into a tarball (b)\. .fi .RE .IP \(bu 2 -\fBnpm install <tarball url>\fR: +\fBnpm install <tarball url>\fP: Fetch the tarball url, and then install it\. In order to distinguish between this and other options, the argument must start with "http://" or "https://" Example: @@ -83,9 +83,9 @@ after packing it up into a tarball (b)\. .fi .RE .IP \(bu 2 -\fBnpm install [@<scope>/]<name> [\-\-save|\-\-save\-dev|\-\-save\-optional]\fR: - Do a \fB<name>@<tag>\fR install, where \fB<tag>\fR is the "tag" config\. (See - npm help 7 \fBnpm\-config\fR\|\.) +\fBnpm install [@<scope>/]<name> [\-\-save|\-\-save\-dev|\-\-save\-optional]\fP: + Do a \fB<name>@<tag>\fP install, where \fB<tag>\fP is the "tag" config\. (See + npm help 7 \fBnpm\-config\fP\|\.) In most cases, this will install the latest version of the module published on npm\. Example: @@ -95,24 +95,24 @@ after packing it up into a tarball (b)\. npm install sax .fi .RE - \fBnpm install\fR takes 3 exclusive, optional flags which save or update + \fBnpm install\fP takes 3 exclusive, optional flags which save or update the package version in your main package\.json: .RS 0 .IP \(bu 2 -\fB\-\-save\fR: Package will appear in your \fBdependencies\fR\|\. +\fB\-\-save\fP: Package will appear in your \fBdependencies\fP\|\. .IP \(bu 2 -\fB\-\-save\-dev\fR: Package will appear in your \fBdevDependencies\fR\|\. +\fB\-\-save\-dev\fP: Package will appear in your \fBdevDependencies\fP\|\. .IP \(bu 2 -\fB\-\-save\-optional\fR: Package will appear in your \fBoptionalDependencies\fR\|\. +\fB\-\-save\-optional\fP: Package will appear in your \fBoptionalDependencies\fP\|\. When using any of the above options to save dependencies to your package\.json, there is an additional, optional flag: .IP \(bu 2 -\fB\-\-save\-exact\fR: Saved dependencies will be configured with an +\fB\-\-save\-exact\fP: Saved dependencies will be configured with an exact version rather than using npm's default semver range operator\. -\fB<scope>\fR is optional\. The package will be downloaded from the registry +\fB<scope>\fP is optional\. The package will be downloaded from the registry associated with the specified scope\. If no registry is associated with -the given scope the default registry is assumed\. See npm help 7 \fBnpm\-scope\fR\|\. +the given scope the default registry is assumed\. See npm help 7 \fBnpm\-scope\fP\|\. Note: if you do not include the @\-symbol on your scope name, npm will interpret this as a GitHub repository instead, see below\. Scopes names must also be followed by a slash\. @@ -142,7 +142,7 @@ fetch the package by name if it is not valid\. .RE .RS 0 .IP \(bu 2 -\fBnpm install [@<scope>/]<name>@<tag>\fR: +\fBnpm install [@<scope>/]<name>@<tag>\fP: Install the version of the package that is referenced by the specified tag\. If the tag does not exist in the registry data for that package, then this will fail\. @@ -155,7 +155,7 @@ fetch the package by name if it is not valid\. .fi .RE .IP \(bu 2 -\fBnpm install [@<scope>/]<name>@<version>\fR: +\fBnpm install [@<scope>/]<name>@<version>\fP: Install the specified version of the package\. This will fail if the version has not been published to the registry\. Example: @@ -167,9 +167,9 @@ fetch the package by name if it is not valid\. .fi .RE .IP \(bu 2 -\fBnpm install [@<scope>/]<name>@<version range>\fR: +\fBnpm install [@<scope>/]<name>@<version range>\fP: Install a version of the package matching the specified version range\. This - will follow the same rules for resolving dependencies described in npm help 5 \fBpackage\.json\fR\|\. + will follow the same rules for resolving dependencies described in npm help 5 \fBpackage\.json\fP\|\. Note that most version ranges must be put in quotes so that your shell will treat it as a single argument\. Example: @@ -181,7 +181,7 @@ fetch the package by name if it is not valid\. .fi .RE .IP \(bu 2 -\fBnpm install <git remote url>\fR: +\fBnpm install <git remote url>\fP: Install a package by cloning a git remote url\. The format of the git url is: .P @@ -190,24 +190,24 @@ fetch the package by name if it is not valid\. <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:/]<path>[#<commit\-ish>] .fi .RE - \fB<protocol>\fR is one of \fBgit\fR, \fBgit+ssh\fR, \fBgit+http\fR, or - \fBgit+https\fR\|\. If no \fB<commit\-ish>\fR is specified, then \fBmaster\fR is + \fB<protocol>\fP is one of \fBgit\fP, \fBgit+ssh\fP, \fBgit+http\fP, or + \fBgit+https\fP\|\. If no \fB<commit\-ish>\fP is specified, then \fBmaster\fP is used\. The following git environment variables are recognized by npm and will be added to the environment when running git: .RS 0 .IP \(bu 2 -\fBGIT_ASKPASS\fR +\fBGIT_ASKPASS\fP .IP \(bu 2 -\fBGIT_PROXY_COMMAND\fR +\fBGIT_PROXY_COMMAND\fP .IP \(bu 2 -\fBGIT_SSH\fR +\fBGIT_SSH\fP .IP \(bu 2 -\fBGIT_SSH_COMMAND\fR +\fBGIT_SSH_COMMAND\fP .IP \(bu 2 -\fBGIT_SSL_CAINFO\fR +\fBGIT_SSL_CAINFO\fP .IP \(bu 2 -\fBGIT_SSL_NO_VERIFY\fR +\fBGIT_SSL_NO_VERIFY\fP See the git man page for details\. Examples: .P @@ -222,12 +222,12 @@ GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\ .RE .IP \(bu 2 -\fBnpm install <githubname>/<githubrepo>[#<commit\-ish>]\fR: +\fBnpm install <githubname>/<githubrepo>[#<commit\-ish>]\fP: .IP \(bu 2 -\fBnpm install github:<githubname>/<githubrepo>[#<commit\-ish>]\fR: - Install the package at \fBhttps://github\.com/githubname/githubrepo\fR by - attempting to clone it using \fBgit\fR\|\. - If you don't specify a \fIcommit\-ish\fR then \fBmaster\fR will be used\. +\fBnpm install github:<githubname>/<githubrepo>[#<commit\-ish>]\fP: + Install the package at \fBhttps://github\.com/githubname/githubrepo\fP by + attempting to clone it using \fBgit\fP\|\. + If you don't specify a \fIcommit\-ish\fR then \fBmaster\fP will be used\. Examples: .P .RS 2 @@ -237,11 +237,11 @@ GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\ .fi .RE .IP \(bu 2 -\fBnpm install gist:[<githubname>/]<gistID>[#<commit\-ish>]\fR: - Install the package at \fBhttps://gist\.github\.com/gistID\fR by attempting to - clone it using \fBgit\fR\|\. The GitHub username associated with the gist is - optional and will not be saved in \fBpackage\.json\fR if \fB\-\-save\fR is used\. - If you don't specify a \fIcommit\-ish\fR then \fBmaster\fR will be used\. +\fBnpm install gist:[<githubname>/]<gistID>[#<commit\-ish>]\fP: + Install the package at \fBhttps://gist\.github\.com/gistID\fP by attempting to + clone it using \fBgit\fP\|\. The GitHub username associated with the gist is + optional and will not be saved in \fBpackage\.json\fP if \fB\-\-save\fP is used\. + If you don't specify a \fIcommit\-ish\fR then \fBmaster\fP will be used\. Example: .P .RS 2 @@ -250,10 +250,10 @@ GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\ .fi .RE .IP \(bu 2 -\fBnpm install bitbucket:<bitbucketname>/<bitbucketrepo>[#<commit\-ish>]\fR: - Install the package at \fBhttps://bitbucket\.org/bitbucketname/bitbucketrepo\fR - by attempting to clone it using \fBgit\fR\|\. - If you don't specify a \fIcommit\-ish\fR then \fBmaster\fR will be used\. +\fBnpm install bitbucket:<bitbucketname>/<bitbucketrepo>[#<commit\-ish>]\fP: + Install the package at \fBhttps://bitbucket\.org/bitbucketname/bitbucketrepo\fP + by attempting to clone it using \fBgit\fP\|\. + If you don't specify a \fIcommit\-ish\fR then \fBmaster\fP will be used\. Example: .P .RS 2 @@ -262,10 +262,10 @@ GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\ .fi .RE .IP \(bu 2 -\fBnpm install gitlab:<gitlabname>/<gitlabrepo>[#<commit\-ish>]\fR: - Install the package at \fBhttps://gitlab\.com/gitlabname/gitlabrepo\fR - by attempting to clone it using \fBgit\fR\|\. - If you don't specify a \fIcommit\-ish\fR then \fBmaster\fR will be used\. +\fBnpm install gitlab:<gitlabname>/<gitlabrepo>[#<commit\-ish>]\fP: + Install the package at \fBhttps://gitlab\.com/gitlabname/gitlabrepo\fP + by attempting to clone it using \fBgit\fP\|\. + If you don't specify a \fIcommit\-ish\fR then \fBmaster\fP will be used\. Example: .P .RS 2 @@ -285,11 +285,11 @@ npm install sax@">=0\.1\.0 <0\.2\.0" bench supervisor .fi .RE .P -The \fB\-\-tag\fR argument will apply to all of the specified install targets\. If a +The \fB\-\-tag\fP argument will apply to all of the specified install targets\. If a tag with the given name exists, the tagged version is preferred over newer versions\. .P -The \fB\-\-force\fR argument will force npm to fetch remote resources even if a +The \fB\-\-force\fP argument will force npm to fetch remote resources even if a local copy exists on disk\. .P .RS 2 @@ -298,25 +298,25 @@ npm install sax \-\-force .fi .RE .P -The \fB\-\-global\fR argument will cause npm to install the package globally -rather than locally\. See npm help 5 \fBnpm\-folders\fR\|\. +The \fB\-\-global\fP argument will cause npm to install the package globally +rather than locally\. See npm help 5 \fBnpm\-folders\fP\|\. .P -The \fB\-\-link\fR argument will cause npm to link global installs into the +The \fB\-\-link\fP argument will cause npm to link global installs into the local space in some cases\. .P -The \fB\-\-no\-bin\-links\fR argument will prevent npm from creating symlinks for +The \fB\-\-no\-bin\-links\fP argument will prevent npm from creating symlinks for any binaries the package might contain\. .P -The \fB\-\-no\-optional\fR argument will prevent optional dependencies from +The \fB\-\-no\-optional\fP argument will prevent optional dependencies from being installed\. .P -The \fB\-\-no\-shrinkwrap\fR argument, which will ignore an available +The \fB\-\-no\-shrinkwrap\fP argument, which will ignore an available shrinkwrap file and use the package\.json instead\. .P -The \fB\-\-nodedir=/path/to/node/source\fR argument will allow npm to find the +The \fB\-\-nodedir=/path/to/node/source\fP argument will allow npm to find the node source code so that npm can compile native modules\. .P -See npm help 7 \fBnpm\-config\fR\|\. Many of the configuration params have some +See npm help 7 \fBnpm\-config\fP\|\. Many of the configuration params have some effect on installation, since that's most of what npm does\. .SH ALGORITHM .P @@ -336,7 +336,7 @@ for each dep@version in what\.dependencies .fi .RE .P -For this \fBpackage{dep}\fR structure: \fBA{B,C}, B{C}, C{D}\fR, +For this \fBpackage{dep}\fP structure: \fBA{B,C}, B{C}, C{D}\fP, this algorithm produces: .P .RS 2 @@ -365,15 +365,15 @@ A \-> B \-> A' \-> B' \-> A \-> B \-> A' \-> B' \-> A \-> \.\.\. .fi .RE .P -where \fBA\fR is some version of a package, and \fBA'\fR is a different version -of the same package\. Because \fBB\fR depends on a different version of \fBA\fR +where \fBA\fP is some version of a package, and \fBA'\fP is a different version +of the same package\. Because \fBB\fP depends on a different version of \fBA\fP than the one that is already in the tree, it must install a separate -copy\. The same is true of \fBA'\fR, which must install \fBB'\fR\|\. Because \fBB'\fR -depends on the original version of \fBA\fR, which has been overridden, the +copy\. The same is true of \fBA'\fP, which must install \fBB'\fP\|\. Because \fBB'\fP +depends on the original version of \fBA\fP, which has been overridden, the cycle falls into infinite regress\. .P To avoid this situation, npm flat\-out refuses to install any -\fBname@version\fR that is already present anywhere in the tree of package +\fBname@version\fP that is already present anywhere in the tree of package folder ancestors\. A more correct, but more complex, solution would be to symlink the existing version into the new location\. If this ever affects a real use\-case, it will be investigated\. diff --git a/deps/npm/man/man1/npm-link.1 b/deps/npm/man/man1/npm-link.1 index e063986b17..8a0c843fa2 100644 --- a/deps/npm/man/man1/npm-link.1 +++ b/deps/npm/man/man1/npm-link.1 @@ -14,20 +14,20 @@ npm ln (with any of the previous argument usage) .P Package linking is a two\-step process\. .P -First, \fBnpm link\fR in a package folder will create a globally\-installed -symbolic link from \fBprefix/package\-name\fR to the current folder (see -npm help 7 \fBnpm\-config\fR for the value of \fBprefix\fR)\. +First, \fBnpm link\fP in a package folder will create a globally\-installed +symbolic link from \fBprefix/package\-name\fP to the current folder (see +npm help 7 \fBnpm\-config\fP for the value of \fBprefix\fP)\. .P -Next, in some other location, \fBnpm link package\-name\fR will create a -symlink from the local \fBnode_modules\fR folder to the global symlink\. +Next, in some other location, \fBnpm link package\-name\fP will create a +symlink from the local \fBnode_modules\fP folder to the global symlink\. .P -Note that \fBpackage\-name\fR is taken from \fBpackage\.json\fR, +Note that \fBpackage\-name\fP is taken from \fBpackage\.json\fP, not from directory name\. .P -The package name can be optionally prefixed with a scope\. See npm help 7 \fBnpm\-scope\fR\|\. +The package name can be optionally prefixed with a scope\. See npm help 7 \fBnpm\-scope\fP\|\. The scope must be preceded by an @\-symbol and followed by a slash\. .P -When creating tarballs for \fBnpm publish\fR, the linked packages are +When creating tarballs for \fBnpm publish\fP, the linked packages are "snapshotted" to their current state by resolving the symbolic links\. .P This is handy for installing your own stuff, so that you can work on it and @@ -68,9 +68,9 @@ npm link node\-redis .RE .P That is, it first creates a global link, and then links the global -installation target into your project's \fBnode_modules\fR folder\. +installation target into your project's \fBnode_modules\fP folder\. .P -If your linked package is scoped (see npm help 7 \fBnpm\-scope\fR) your link command must +If your linked package is scoped (see npm help 7 \fBnpm\-scope\fP) your link command must include that scope, e\.g\. .P .RS 2 diff --git a/deps/npm/man/man1/npm-logout.1 b/deps/npm/man/man1/npm-logout.1 index e5e0b99690..379b9b0306 100644 --- a/deps/npm/man/man1/npm-logout.1 +++ b/deps/npm/man/man1/npm-logout.1 @@ -18,21 +18,21 @@ When logged into a legacy registry that uses username and password authenticatio clear the credentials in your user configuration\. In this case, it will \fIonly\fR affect the current environment\. .P -If \fB\-\-scope\fR is provided, this will find the credentials for the registry +If \fB\-\-scope\fP is provided, this will find the credentials for the registry connected to that scope, if set\. .SH CONFIGURATION .SS registry .P Default: http://registry\.npmjs\.org/ .P -The base URL of the npm package registry\. If \fBscope\fR is also specified, +The base URL of the npm package registry\. If \fBscope\fP is also specified, it takes precedence\. .SS scope .P Default: none .P If specified, the user and login credentials given will be associated -with the specified scope\. See npm help 7 \fBnpm\-scope\fR\|\. You can use both at the same time, +with the specified scope\. See npm help 7 \fBnpm\-scope\fP\|\. You can use both at the same time, e\.g\. .P .RS 2 diff --git a/deps/npm/man/man1/npm-ls.1 b/deps/npm/man/man1/npm-ls.1 index 9220bef024..a052542697 100644 --- a/deps/npm/man/man1/npm-ls.1 +++ b/deps/npm/man/man1/npm-ls.1 @@ -16,14 +16,14 @@ npm ll [[@<scope>/]<pkg> \.\.\.] This command will print to stdout all the versions of packages that are installed, as well as their dependencies, in a tree\-structure\. .P -Positional arguments are \fBname@version\-range\fR identifiers, which will +Positional arguments are \fBname@version\-range\fP identifiers, which will limit the results to only the paths to the packages named\. Note that nested packages will \fIalso\fR show the paths to the specified packages\. -For example, running \fBnpm ls promzard\fR in npm's source tree will show: +For example, running \fBnpm ls promzard\fP in npm's source tree will show: .P .RS 2 .nf -npm@2.13.1 /path/to/npm +npm@2.13.2 /path/to/npm └─┬ init\-package\-json@0\.0\.4 └── promzard@0\.1\.5 .fi @@ -35,7 +35,7 @@ If a project specifies git urls for dependencies these are shown in parentheses after the name@version to make it easier for users to recognize potential forks of a project\. .P -When run as \fBll\fR or \fBla\fR, it shows extended information by default\. +When run as \fBll\fP or \fBla\fP, it shows extended information by default\. .SH CONFIGURATION .SS json .RS 0 @@ -95,7 +95,7 @@ Default: false .RE .P -Display only the dependency tree for packages in \fBdependencies\fR\|\. +Display only the dependency tree for packages in \fBdependencies\fP\|\. .SS dev .RS 0 .IP \(bu 2 @@ -105,7 +105,7 @@ Default: false .RE .P -Display only the dependency tree for packages in \fBdevDependencies\fR\|\. +Display only the dependency tree for packages in \fBdevDependencies\fP\|\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-pack.1 b/deps/npm/man/man1/npm-pack.1 index 7781bbdbd1..a630def97a 100644 --- a/deps/npm/man/man1/npm-pack.1 +++ b/deps/npm/man/man1/npm-pack.1 @@ -13,7 +13,7 @@ npm pack [<pkg> [<pkg> \.\.\.]] For anything that's installable (that is, a package folder, tarball, tarball url, name@tag, name@version, or name), this command will fetch it to the cache, and then copy the tarball to the current working -directory as \fB<name>\-<version>\.tgz\fR, and then write the filenames out to +directory as \fB<name>\-<version>\.tgz\fP, and then write the filenames out to stdout\. .P If the same package is specified multiple times, then the file will be diff --git a/deps/npm/man/man1/npm-prefix.1 b/deps/npm/man/man1/npm-prefix.1 index 1f42ea7a75..1bc68d0c0d 100644 --- a/deps/npm/man/man1/npm-prefix.1 +++ b/deps/npm/man/man1/npm-prefix.1 @@ -11,10 +11,10 @@ npm prefix [\-g] .SH DESCRIPTION .P Print the local prefix to standard out\. This is the closest parent directory -to contain a package\.json file unless \fB\-g\fR is also specified\. +to contain a package\.json file unless \fB\-g\fP is also specified\. .P -If \fB\-g\fR is specified, this will be the value of the global prefix\. See -npm help 7 \fBnpm\-config\fR for more detail\. +If \fB\-g\fP is specified, this will be the value of the global prefix\. See +npm help 7 \fBnpm\-config\fP for more detail\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-prune.1 b/deps/npm/man/man1/npm-prune.1 index 304dcece16..937fbb34f1 100644 --- a/deps/npm/man/man1/npm-prune.1 +++ b/deps/npm/man/man1/npm-prune.1 @@ -18,10 +18,10 @@ removed\. Extraneous packages are packages that are not listed on the parent package's dependencies list\. .P -If the \fB\-\-production\fR flag is specified or the \fBNODE_ENV\fR environment -variable is set to \fBproduction\fR, this command will remove the packages -specified in your \fBdevDependencies\fR\|\. Setting \fB\-\-production=false\fR will -negate \fBNODE_ENV\fR being set to \fBproduction\fR\|\. +If the \fB\-\-production\fP flag is specified or the \fBNODE_ENV\fP environment +variable is set to \fBproduction\fP, this command will remove the packages +specified in your \fBdevDependencies\fP\|\. Setting \fB\-\-production=false\fP will +negate \fBNODE_ENV\fP being set to \fBproduction\fP\|\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-publish.1 b/deps/npm/man/man1/npm-publish.1 index 0daaae7d56..a6cab55193 100644 --- a/deps/npm/man/man1/npm-publish.1 +++ b/deps/npm/man/man1/npm-publish.1 @@ -12,30 +12,30 @@ npm publish <folder> [\-\-tag <tag>] [\-\-access <public|restricted>] .SH DESCRIPTION .P Publishes a package to the registry so that it can be installed by name\. See -npm help 7 \fBnpm\-developers\fR for details on what's included in the published package, as +npm help 7 \fBnpm\-developers\fP for details on what's included in the published package, as well as details on how the package is built\. .P By default npm will publish to the public registry\. This can be overridden by -specifying a different default registry or using a npm help 7 \fBnpm\-scope\fR in the name -(see npm help 5 \fBpackage\.json\fR)\. +specifying a different default registry or using a npm help 7 \fBnpm\-scope\fP in the name +(see npm help 5 \fBpackage\.json\fP)\. .RS 0 .IP \(bu 2 -\fB<folder>\fR: +\fB<folder>\fP: A folder containing a package\.json file .IP \(bu 2 -\fB<tarball>\fR: +\fB<tarball>\fP: A url or file path to a gzipped tar archive containing a single folder with a package\.json file inside\. .IP \(bu 2 -\fB[\-\-tag <tag>]\fR +\fB[\-\-tag <tag>]\fP Registers the published package with the given tag, such that \fBnpm install -<name>@<tag>\fR will install this version\. By default, \fBnpm publish\fR updates -and \fBnpm install\fR installs the \fBlatest\fR tag\. +<name>@<tag>\fP will install this version\. By default, \fBnpm publish\fP updates +and \fBnpm install\fP installs the \fBlatest\fP tag\. .IP \(bu 2 -\fB[\-\-access <public|restricted>]\fR +\fB[\-\-access <public|restricted>]\fP Tells the registry whether this package should be published as public or -restricted\. Only applies to scoped packages, which default to \fBrestricted\fR\|\. -If you don't have a paid account, you must publish with \fB\-\-access public\fR +restricted\. Only applies to scoped packages, which default to \fBrestricted\fP\|\. +If you don't have a paid account, you must publish with \fB\-\-access public\fP to publish scoped packages\. .RE diff --git a/deps/npm/man/man1/npm-rebuild.1 b/deps/npm/man/man1/npm-rebuild.1 index d3c1c615bb..7e890d50b5 100644 --- a/deps/npm/man/man1/npm-rebuild.1 +++ b/deps/npm/man/man1/npm-rebuild.1 @@ -11,13 +11,13 @@ npm rb [<name> [<name> \.\.\.]] .RE .RS 0 .IP \(bu 2 -\fB<name>\fR: +\fB<name>\fP: The package to rebuild .RE .SH DESCRIPTION .P -This command runs the \fBnpm build\fR command on the matched folders\. This is useful +This command runs the \fBnpm build\fP command on the matched folders\. This is useful when you install a new version of node, and must recompile all your C++ addons with the new binary\. .SH SEE ALSO diff --git a/deps/npm/man/man1/npm-repo.1 b/deps/npm/man/man1/npm-repo.1 index a6638b0078..477f87a3c5 100644 --- a/deps/npm/man/man1/npm-repo.1 +++ b/deps/npm/man/man1/npm-repo.1 @@ -12,20 +12,20 @@ npm repo (with no args in a package dir) .SH DESCRIPTION .P This command tries to guess at the likely location of a package's -repository URL, and then tries to open it using the \fB\-\-browser\fR +repository URL, and then tries to open it using the \fB\-\-browser\fP config param\. If no package name is provided, it will search for -a \fBpackage\.json\fR in the current folder and use the \fBname\fR property\. +a \fBpackage\.json\fP in the current folder and use the \fBname\fP property\. .SH CONFIGURATION .SS browser .RS 0 .IP \(bu 2 -Default: OS X: \fB"open"\fR, Windows: \fB"start"\fR, Others: \fB"xdg\-open"\fR +Default: OS X: \fB"open"\fP, Windows: \fB"start"\fP, Others: \fB"xdg\-open"\fP .IP \(bu 2 Type: String .RE .P -The browser that is called by the \fBnpm repo\fR command to open websites\. +The browser that is called by the \fBnpm repo\fP command to open websites\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-restart.1 b/deps/npm/man/man1/npm-restart.1 index ec21ac709c..bbfd94f741 100644 --- a/deps/npm/man/man1/npm-restart.1 +++ b/deps/npm/man/man1/npm-restart.1 @@ -40,7 +40,7 @@ postrestart Note that the "restart" script is run \fBin addition to\fR the "stop" and "start" scripts, not instead of them\. .P -This is the behavior as of \fBnpm\fR major version 2\. A change in this +This is the behavior as of \fBnpm\fP major version 2\. A change in this behavior will be accompanied by an increase in major version number .SH SEE ALSO .RS 0 diff --git a/deps/npm/man/man1/npm-root.1 b/deps/npm/man/man1/npm-root.1 index 8c80364536..7f3c87b76e 100644 --- a/deps/npm/man/man1/npm-root.1 +++ b/deps/npm/man/man1/npm-root.1 @@ -10,7 +10,7 @@ npm root .RE .SH DESCRIPTION .P -Print the effective \fBnode_modules\fR folder to standard out\. +Print the effective \fBnode_modules\fP folder to standard out\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-run-script.1 b/deps/npm/man/man1/npm-run-script.1 index c1d893beb5..51c94d9d41 100644 --- a/deps/npm/man/man1/npm-run-script.1 +++ b/deps/npm/man/man1/npm-run-script.1 @@ -11,16 +11,16 @@ npm run [command] [\-\- <args>] .RE .SH DESCRIPTION .P -This runs an arbitrary command from a package's \fB"scripts"\fR object\. If no -\fB"command"\fR is provided, it will list the available scripts\. \fBrun[\-script]\fR is +This runs an arbitrary command from a package's \fB"scripts"\fP object\. If no +\fB"command"\fP is provided, it will list the available scripts\. \fBrun[\-script]\fP is used by the test, start, restart, and stop commands, but can be called directly, as well\. When the scripts in the package are printed out, they're separated into lifecycle (test, start, restart) and directly\-run scripts\. .P -As of \fBnpm@2\.0\.0\fR \fIhttp://blog\.npmjs\.org/post/98131109725/npm\-2\-0\-0\fR, you can -use custom arguments when executing scripts\. The special option \fB\-\-\fR is used by +As of \fBnpm@2\.0\.0\fP \fIhttp://blog\.npmjs\.org/post/98131109725/npm\-2\-0\-0\fR, you can +use custom arguments when executing scripts\. The special option \fB\-\-\fP is used by getopt \fIhttp://goo\.gl/KxMmtG\fR to delimit the end of the options\. npm will pass -all the arguments after the \fB\-\-\fR directly to your script: +all the arguments after the \fB\-\-\fP directly to your script: .P .RS 2 .nf @@ -28,18 +28,18 @@ npm run test \-\- \-\-grep="pattern" .fi .RE .P -The arguments will only be passed to the script specified after \fBnpm run\fR +The arguments will only be passed to the script specified after \fBnpm run\fP and not to any pre or post script\. .P -The \fBenv\fR script is a special built\-in command that can be used to list +The \fBenv\fP script is a special built\-in command that can be used to list environment variables that will be available to the script at runtime\. If an "env" command is defined in your package it will take precedence over the built\-in\. .P -In addition to the shell's pre\-existing \fBPATH\fR, \fBnpm run\fR adds -\fBnode_modules/\.bin\fR to the \fBPATH\fR provided to scripts\. Any binaries provided by -locally\-installed dependencies can be used without the \fBnode_modules/\.bin\fR -prefix\. For example, if there is a \fBdevDependency\fR on \fBtap\fR in your package, +In addition to the shell's pre\-existing \fBPATH\fP, \fBnpm run\fP adds +\fBnode_modules/\.bin\fP to the \fBPATH\fP provided to scripts\. Any binaries provided by +locally\-installed dependencies can be used without the \fBnode_modules/\.bin\fP +prefix\. For example, if there is a \fBdevDependency\fP on \fBtap\fP in your package, you should write: .P .RS 2 @@ -48,7 +48,7 @@ you should write: .fi .RE .P -instead of \fB"scripts": {"test": "node_modules/\.bin/tap test/\\*\.js"}\fR to run your tests\. +instead of \fB"scripts": {"test": "node_modules/\.bin/tap test/\\*\.js"}\fP to run your tests\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-search.1 b/deps/npm/man/man1/npm-search.1 index 5081cf32eb..d911055094 100644 --- a/deps/npm/man/man1/npm-search.1 +++ b/deps/npm/man/man1/npm-search.1 @@ -14,8 +14,8 @@ npm se [search terms \.\.\.] .P Search the registry for packages matching the search terms\. .P -If a term starts with \fB/\fR, then it's interpreted as a regular expression\. -A trailing \fB/\fR will be ignored in this case\. (Note that many regular +If a term starts with \fB/\fP, then it's interpreted as a regular expression\. +A trailing \fB/\fP will be ignored in this case\. (Note that many regular expression characters must be escaped or quoted in most shells\.) .SH CONFIGURATION .SS long diff --git a/deps/npm/man/man1/npm-shrinkwrap.1 b/deps/npm/man/man1/npm-shrinkwrap.1 index e0eb3ce1b4..7b3569a172 100644 --- a/deps/npm/man/man1/npm-shrinkwrap.1 +++ b/deps/npm/man/man1/npm-shrinkwrap.1 @@ -12,18 +12,18 @@ npm shrinkwrap .P This command locks down the versions of a package's dependencies so that you can control exactly which versions of each dependency will be -used when your package is installed\. The \fBpackage\.json\fR file is still -required if you want to use \fBnpm install\fR\|\. +used when your package is installed\. The \fBpackage\.json\fP file is still +required if you want to use \fBnpm install\fP\|\. .P -By default, \fBnpm install\fR recursively installs the target's -dependencies (as specified in \fBpackage\.json\fR), choosing the latest +By default, \fBnpm install\fP recursively installs the target's +dependencies (as specified in \fBpackage\.json\fP), choosing the latest available version that satisfies the dependency's semver pattern\. In some situations, particularly when shipping software where each change is tightly managed, it's desirable to fully specify each version of each dependency recursively so that subsequent builds and deploys do not inadvertently pick up newer versions of a dependency that satisfy the semver pattern\. Specifying specific semver patterns in each -dependency's \fBpackage\.json\fR would facilitate this, but that's not always +dependency's \fBpackage\.json\fP would facilitate this, but that's not always possible or desirable, as when another author owns the npm package\. It's also possible to check dependencies directly into source control, but that may be undesirable for other reasons\. @@ -68,7 +68,7 @@ and package C: .RE .P If these are the only versions of A, B, and C available in the -registry, then a normal \fBnpm install A\fR will install: +registry, then a normal \fBnpm install A\fP will install: .P .RS 2 .nf @@ -78,7 +78,7 @@ A@0\.1\.0 .fi .RE .P -However, if B@0\.0\.2 is published, then a fresh \fBnpm install A\fR will +However, if B@0\.0\.2 is published, then a fresh \fBnpm install A\fP will install: .P .RS 2 @@ -105,7 +105,7 @@ npm shrinkwrap .fi .RE .P -This generates \fBnpm\-shrinkwrap\.json\fR, which will look something like this: +This generates \fBnpm\-shrinkwrap\.json\fP, which will look something like this: .P .RS 2 .nf @@ -127,30 +127,30 @@ This generates \fBnpm\-shrinkwrap\.json\fR, which will look something like this: .RE .P The shrinkwrap command has locked down the dependencies based on -what's currently installed in node_modules\. When \fBnpm install\fR -installs a package with an \fBnpm\-shrinkwrap\.json\fR in the package -root, the shrinkwrap file (rather than \fBpackage\.json\fR files) completely +what's currently installed in node_modules\. When \fBnpm install\fP +installs a package with an \fBnpm\-shrinkwrap\.json\fP in the package +root, the shrinkwrap file (rather than \fBpackage\.json\fP files) completely drives the installation of that package and all of its dependencies (recursively)\. So now the author publishes A@0\.1\.0, and subsequent installs of this package will use B@0\.0\.1 and C@0\.0\.1, regardless the -dependencies and versions listed in A's, B's, and C's \fBpackage\.json\fR +dependencies and versions listed in A's, B's, and C's \fBpackage\.json\fP files\. .SS Using shrinkwrapped packages .P Using a shrinkwrapped package is no different than using any other -package: you can \fBnpm install\fR it by hand, or add a dependency to your -\fBpackage\.json\fR file and \fBnpm install\fR it\. +package: you can \fBnpm install\fP it by hand, or add a dependency to your +\fBpackage\.json\fP file and \fBnpm install\fP it\. .SS Building shrinkwrapped packages .P To shrinkwrap an existing package: .RS 0 .IP 1. 3 -Run \fBnpm install\fR in the package root to install the current +Run \fBnpm install\fP in the package root to install the current versions of all dependencies\. .IP 2. 3 Validate that the package works as expected with these versions\. .IP 3. 3 -Run \fBnpm shrinkwrap\fR, add \fBnpm\-shrinkwrap\.json\fR to git, and publish +Run \fBnpm shrinkwrap\fP, add \fBnpm\-shrinkwrap\.json\fP to git, and publish your package\. .RE @@ -158,19 +158,19 @@ your package\. To add or update a dependency in a shrinkwrapped package: .RS 0 .IP 1. 3 -Run \fBnpm install\fR in the package root to install the current +Run \fBnpm install\fP in the package root to install the current versions of all dependencies\. .IP 2. 3 -Add or update dependencies\. \fBnpm install\fR each new or updated -package individually and then update \fBpackage\.json\fR\|\. Note that they +Add or update dependencies\. \fBnpm install\fP each new or updated +package individually and then update \fBpackage\.json\fP\|\. Note that they must be explicitly named in order to be installed: running \fBnpm -install\fR with no arguments will merely reproduce the existing +install\fP with no arguments will merely reproduce the existing shrinkwrap\. .IP 3. 3 Validate that the package works as expected with the new dependencies\. .IP 4. 3 -Run \fBnpm shrinkwrap\fR, commit the new \fBnpm\-shrinkwrap\.json\fR, and +Run \fBnpm shrinkwrap\fP, commit the new \fBnpm\-shrinkwrap\.json\fP, and publish your package\. .RE @@ -179,19 +179,19 @@ You can use npm help outdated to view dependencies with newer versions available\. .SS Other Notes .P -A shrinkwrap file must be consistent with the package's \fBpackage\.json\fR -file\. \fBnpm shrinkwrap\fR will fail if required dependencies are not +A shrinkwrap file must be consistent with the package's \fBpackage\.json\fP +file\. \fBnpm shrinkwrap\fP will fail if required dependencies are not already installed, since that would result in a shrinkwrap that wouldn't actually work\. Similarly, the command will fail if there are -extraneous packages (not referenced by \fBpackage\.json\fR), since that would -indicate that \fBpackage\.json\fR is not correct\. +extraneous packages (not referenced by \fBpackage\.json\fP), since that would +indicate that \fBpackage\.json\fP is not correct\. .P -Since \fBnpm shrinkwrap\fR is intended to lock down your dependencies for -production use, \fBdevDependencies\fR will not be included unless you -explicitly set the \fB\-\-dev\fR flag when you run \fBnpm shrinkwrap\fR\|\. If -installed \fBdevDependencies\fR are excluded, then npm will print a +Since \fBnpm shrinkwrap\fP is intended to lock down your dependencies for +production use, \fBdevDependencies\fP will not be included unless you +explicitly set the \fB\-\-dev\fP flag when you run \fBnpm shrinkwrap\fP\|\. If +installed \fBdevDependencies\fP are excluded, then npm will print a warning\. If you want them to be installed with your module by -default, please consider adding them to \fBdependencies\fR instead\. +default, please consider adding them to \fBdependencies\fP instead\. .P If shrinkwrapped package A depends on shrinkwrapped package B, B's shrinkwrap will not be used as part of the installation of A\. However, diff --git a/deps/npm/man/man1/npm-tag.1 b/deps/npm/man/man1/npm-tag.1 index 6fb58d1d37..606270e9b4 100644 --- a/deps/npm/man/man1/npm-tag.1 +++ b/deps/npm/man/man1/npm-tag.1 @@ -13,7 +13,7 @@ npm tag <name>@<version> [<tag>] THIS COMMAND IS DEPRECATED\. See npm help dist\-tag for details\. .P Tags the specified version of the package with the specified tag, or the -\fB\-\-tag\fR config if not specified\. +\fB\-\-tag\fP config if not specified\. .P A tag can be used when installing packages as a reference to a version instead of using a specific version number: @@ -32,13 +32,13 @@ npm install \-\-tag <tag> .fi .RE .P -This also applies to \fBnpm dedupe\fR\|\. +This also applies to \fBnpm dedupe\fP\|\. .P Publishing a package always sets the "latest" tag to the published version\. .SH PURPOSE .P Tags can be used to provide an alias instead of version numbers\. For -example, \fBnpm\fR currently uses the tag "next" to identify the upcoming +example, \fBnpm\fP currently uses the tag "next" to identify the upcoming version, and the tag "latest" to identify the current version\. .P A project might choose to have multiple streams of development, e\.g\., @@ -46,16 +46,16 @@ A project might choose to have multiple streams of development, e\.g\., .SH CAVEATS .P Tags must share a namespace with version numbers, because they are -specified in the same slot: \fBnpm install <pkg>@<version>\fR vs \fBnpm -install <pkg>@<tag>\fR\|\. +specified in the same slot: \fBnpm install <pkg>@<version>\fP vs \fBnpm +install <pkg>@<tag>\fP\|\. .P Tags that can be interpreted as valid semver ranges will be -rejected\. For example, \fBv1\.4\fR cannot be used as a tag, because it is -interpreted by semver as \fB>=1\.4\.0 <1\.5\.0\fR\|\. See +rejected\. For example, \fBv1\.4\fP cannot be used as a tag, because it is +interpreted by semver as \fB>=1\.4\.0 <1\.5\.0\fP\|\. See https://github\.com/npm/npm/issues/6082\|\. .P The simplest way to avoid semver problems with tags is to use tags -that do not begin with a number or the letter \fBv\fR\|\. +that do not begin with a number or the letter \fBv\fP\|\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-test.1 b/deps/npm/man/man1/npm-test.1 index 5a07a46553..658b8e9cce 100644 --- a/deps/npm/man/man1/npm-test.1 +++ b/deps/npm/man/man1/npm-test.1 @@ -13,7 +13,7 @@ .P This runs a package's "test" script, if one was provided\. .P -To run tests as a condition of installation, set the \fBnpat\fR config to +To run tests as a condition of installation, set the \fBnpat\fP config to true\. .SH SEE ALSO .RS 0 diff --git a/deps/npm/man/man1/npm-uninstall.1 b/deps/npm/man/man1/npm-uninstall.1 index aef162fab2..11bb0c235f 100644 --- a/deps/npm/man/man1/npm-uninstall.1 +++ b/deps/npm/man/man1/npm-uninstall.1 @@ -22,22 +22,22 @@ npm uninstall sax .fi .RE .P -In global mode (ie, with \fB\-g\fR or \fB\-\-global\fR appended to the command), +In global mode (ie, with \fB\-g\fP or \fB\-\-global\fP appended to the command), it uninstalls the current package context as a global package\. .P -\fBnpm uninstall\fR takes 3 exclusive, optional flags which save or update +\fBnpm uninstall\fP takes 3 exclusive, optional flags which save or update the package version in your main package\.json: .RS 0 .IP \(bu 2 -\fB\-\-save\fR: Package will be removed from your \fBdependencies\fR\|\. +\fB\-\-save\fP: Package will be removed from your \fBdependencies\fP\|\. .IP \(bu 2 -\fB\-\-save\-dev\fR: Package will be removed from your \fBdevDependencies\fR\|\. +\fB\-\-save\-dev\fP: Package will be removed from your \fBdevDependencies\fP\|\. .IP \(bu 2 -\fB\-\-save\-optional\fR: Package will be removed from your \fBoptionalDependencies\fR\|\. +\fB\-\-save\-optional\fP: Package will be removed from your \fBoptionalDependencies\fP\|\. .RE .P -Scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fR\|\. +Scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\. .P Examples: .P diff --git a/deps/npm/man/man1/npm-unpublish.1 b/deps/npm/man/man1/npm-unpublish.1 index c6be18c787..dbb4bf91e4 100644 --- a/deps/npm/man/man1/npm-unpublish.1 +++ b/deps/npm/man/man1/npm-unpublish.1 @@ -13,7 +13,7 @@ npm unpublish [@<scope>/]<name>[@<version>] \fBIt is generally considered bad behavior to remove versions of a library that others are depending on!\fR .P -Consider using the \fBdeprecate\fR command +Consider using the \fBdeprecate\fP command instead, if your intent is to encourage users to upgrade\. .P There is plenty of room on the registry\. @@ -29,7 +29,7 @@ Even if a package version is unpublished, that specific name and version combination can never be reused\. In order to publish the package again, a new version number must be used\. .P -The scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fR\|\. +The scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm-update.1 b/deps/npm/man/man1/npm-update.1 index 9945f4704a..d9afff56cd 100644 --- a/deps/npm/man/man1/npm-update.1 +++ b/deps/npm/man/man1/npm-update.1 @@ -11,26 +11,26 @@ npm update [\-g] [<name> [<name> \.\.\.]] .SH DESCRIPTION .P This command will update all the packages listed to the latest version -(specified by the \fBtag\fR config), respecting semver\. +(specified by the \fBtag\fP config), respecting semver\. .P It will also install missing packages\. As with all commands that install -packages, the \fB\-\-dev\fR flag will cause \fBdevDependencies\fR to be processed +packages, the \fB\-\-dev\fP flag will cause \fBdevDependencies\fP to be processed as well\. .P -If the \fB\-g\fR flag is specified, this command will update globally installed +If the \fB\-g\fP flag is specified, this command will update globally installed packages\. .P If no package name is specified, all packages in the specified location (global or local) will be updated\. .P -As of \fBnpm@2\.6\.1\fR, the \fBnpm update\fR will only inspect top\-level packages\. -Prior versions of \fBnpm\fR would also recursively inspect all dependencies\. -To get the old behavior, use \fBnpm \-\-depth 9999 update\fR, but be warned that -simultaneous asynchronous update of all packages, including \fBnpm\fR itself -and packages that \fBnpm\fR depends on, often causes problems up to and including -the uninstallation of \fBnpm\fR itself\. +As of \fBnpm@2\.6\.1\fP, the \fBnpm update\fP will only inspect top\-level packages\. +Prior versions of \fBnpm\fP would also recursively inspect all dependencies\. +To get the old behavior, use \fBnpm \-\-depth 9999 update\fP, but be warned that +simultaneous asynchronous update of all packages, including \fBnpm\fP itself +and packages that \fBnpm\fP depends on, often causes problems up to and including +the uninstallation of \fBnpm\fP itself\. .P -To restore a missing \fBnpm\fR, use the command: +To restore a missing \fBnpm\fP, use the command: .P .RS 2 .nf @@ -39,12 +39,12 @@ curl \-L https://npmjs\.com/install\.sh | sh .RE .SH EXAMPLES .P -IMPORTANT VERSION NOTE: these examples assume \fBnpm@2\.6\.1\fR or later\. For -older versions of \fBnpm\fR, you must specify \fB\-\-depth 0\fR to get the behavior +IMPORTANT VERSION NOTE: these examples assume \fBnpm@2\.6\.1\fP or later\. For +older versions of \fBnpm\fP, you must specify \fB\-\-depth 0\fP to get the behavior described below\. .P -For the examples below, assume that the current package is \fBapp\fR and it depends -on dependencies, \fBdep1\fR (\fBdep2\fR, \.\. etc\.)\. The published versions of \fBdep1\fR are: +For the examples below, assume that the current package is \fBapp\fP and it depends +on dependencies, \fBdep1\fP (\fBdep2\fP, \.\. etc\.)\. The published versions of \fBdep1\fP are: .P .RS 2 .nf @@ -65,7 +65,7 @@ on dependencies, \fBdep1\fR (\fBdep2\fR, \.\. etc\.)\. The published versions o .RE .SS Caret Dependencies .P -If \fBapp\fR\|'s \fBpackage\.json\fR contains: +If \fBapp\fP\|'s \fBpackage\.json\fP contains: .P .RS 2 .nf @@ -75,11 +75,11 @@ dependencies: { .fi .RE .P -Then \fBnpm update\fR will install \fBdep1@1\.2\.2\fR, because \fB1\.2\.2\fR is \fBlatest\fR and -\fB1\.2\.2\fR satisfies \fB^1\.1\.1\fR\|\. +Then \fBnpm update\fP will install \fBdep1@1\.2\.2\fP, because \fB1\.2\.2\fP is \fBlatest\fP and +\fB1\.2\.2\fP satisfies \fB^1\.1\.1\fP\|\. .SS Tilde Dependencies .P -However, if \fBapp\fR\|'s \fBpackage\.json\fR contains: +However, if \fBapp\fP\|'s \fBpackage\.json\fP contains: .P .RS 2 .nf @@ -89,13 +89,13 @@ dependencies: { .fi .RE .P -In this case, running \fBnpm update\fR will install \fBdep1@1\.1\.2\fR\|\. Even though the \fBlatest\fR -tag points to \fB1\.2\.2\fR, this version does not satisfy \fB~1\.1\.1\fR, which is equivalent -to \fB>=1\.1\.1 <1\.2\.0\fR\|\. So the highest\-sorting version that satisfies \fB~1\.1\.1\fR is used, -which is \fB1\.1\.2\fR\|\. +In this case, running \fBnpm update\fP will install \fBdep1@1\.1\.2\fP\|\. Even though the \fBlatest\fP +tag points to \fB1\.2\.2\fP, this version does not satisfy \fB~1\.1\.1\fP, which is equivalent +to \fB>=1\.1\.1 <1\.2\.0\fP\|\. So the highest\-sorting version that satisfies \fB~1\.1\.1\fP is used, +which is \fB1\.1\.2\fP\|\. .SS Caret Dependencies below 1\.0\.0 .P -Suppose \fBapp\fR has a caret dependency on a version below \fB1\.0\.0\fR, for example: +Suppose \fBapp\fP has a caret dependency on a version below \fB1\.0\.0\fP, for example: .P .RS 2 .nf @@ -105,10 +105,10 @@ dependencies: { .fi .RE .P -\fBnpm update\fR will install \fBdep1@0\.2\.0\fR, because there are no other -versions which satisfy \fB^0\.2\.0\fR\|\. +\fBnpm update\fP will install \fBdep1@0\.2\.0\fP, because there are no other +versions which satisfy \fB^0\.2\.0\fP\|\. .P -If the dependence were on \fB^0\.4\.0\fR: +If the dependence were on \fB^0\.4\.0\fP: .P .RS 2 .nf @@ -118,13 +118,13 @@ dependencies: { .fi .RE .P -Then \fBnpm update\fR will install \fBdep1@0\.4\.1\fR, because that is the highest\-sorting -version that satisfies \fB^0\.4\.0\fR (\fB>= 0\.4\.0 <0\.5\.0\fR) -.SS Recording Updates with \fB\-\-save\fR +Then \fBnpm update\fP will install \fBdep1@0\.4\.1\fP, because that is the highest\-sorting +version that satisfies \fB^0\.4\.0\fP (\fB>= 0\.4\.0 <0\.5\.0\fP) +.SS Recording Updates with \fB\-\-save\fP .P When you want to update a package and save the new version as -the minimum required dependency in \fBpackage\.json\fR, you can use -\fBnpm update \-\-save\fR\|\. For example if \fBpackage\.json\fR contains +the minimum required dependency in \fBpackage\.json\fP, you can use +\fBnpm update \-\-save\fP\|\. For example if \fBpackage\.json\fP contains .P .RS 2 .nf @@ -134,8 +134,8 @@ dependencies: { .fi .RE .P -Then \fBnpm update \-\-save\fR will install \fBdep1@1\.2\.2\fR (i\.e\., \fBlatest\fR), -and \fBpackage\.json\fR will be modified: +Then \fBnpm update \-\-save\fP will install \fBdep1@1\.2\.2\fP (i\.e\., \fBlatest\fP), +and \fBpackage\.json\fP will be modified: .P .RS 2 .nf @@ -145,15 +145,15 @@ dependencies: { .fi .RE .P -Note that \fBnpm\fR will only write an updated version to \fBpackage\.json\fR +Note that \fBnpm\fP will only write an updated version to \fBpackage\.json\fP if it installs a new package\. .SS Updating Globally\-Installed Packages .P -\fBnpm update \-g\fR will apply the \fBupdate\fR action to each globally\- installed -package that is \fBoutdated\fR \-\- that is, has a version that is different from -\fBlatest\fR\|\. +\fBnpm update \-g\fP will apply the \fBupdate\fP action to each globally\- installed +package that is \fBoutdated\fP \-\- that is, has a version that is different from +\fBlatest\fP\|\. .P -NOTE: If a package has been upgraded to a version newer than \fBlatest\fR, it will +NOTE: If a package has been upgraded to a version newer than \fBlatest\fP, it will be \fIdowngraded\fR\|\. .SH SEE ALSO .RS 0 diff --git a/deps/npm/man/man1/npm-version.1 b/deps/npm/man/man1/npm-version.1 index ee696570c8..1d72440fe1 100644 --- a/deps/npm/man/man1/npm-version.1 +++ b/deps/npm/man/man1/npm-version.1 @@ -11,22 +11,22 @@ npm version [<newversion> | major | minor | patch | premajor | preminor | prepat .SH DESCRIPTION .P Run this in a package directory to bump the version and write the new -data back to \fBpackage\.json\fR and, if present, \fBnpm\-shrinkwrap\.json\fR\|\. +data back to \fBpackage\.json\fP and, if present, \fBnpm\-shrinkwrap\.json\fP\|\. .P -The \fBnewversion\fR argument should be a valid semver string, \fIor\fR a -valid second argument to semver\.inc (one of \fBpatch\fR, \fBminor\fR, \fBmajor\fR, -\fBprepatch\fR, \fBpreminor\fR, \fBpremajor\fR, \fBprerelease\fR)\. In the second case, +The \fBnewversion\fP argument should be a valid semver string, \fIor\fR a +valid second argument to semver\.inc (one of \fBpatch\fP, \fBminor\fP, \fBmajor\fP, +\fBprepatch\fP, \fBpreminor\fP, \fBpremajor\fP, \fBprerelease\fP)\. In the second case, the existing version will be incremented by 1 in the specified field\. .P If run in a git repo, it will also create a version commit and tag\. -This behavior is controlled by \fBgit\-tag\-version\fR (see below), and can -be disabled on the command line by running \fBnpm \-\-no\-git\-tag\-version version\fR\|\. -It will fail if the working directory is not clean, unless the \fB\-\-force\fR +This behavior is controlled by \fBgit\-tag\-version\fP (see below), and can +be disabled on the command line by running \fBnpm \-\-no\-git\-tag\-version version\fP\|\. +It will fail if the working directory is not clean, unless the \fB\-\-force\fP flag is set\. .P -If supplied with \fB\-\-message\fR (shorthand: \fB\-m\fR) config option, npm will +If supplied with \fB\-\-message\fP (shorthand: \fB\-m\fP) config option, npm will use it as a commit message when creating a version commit\. If the -\fBmessage\fR config contains \fB%s\fR then that will be replaced with the +\fBmessage\fP config contains \fB%s\fP then that will be replaced with the resulting version number\. For example: .P .RS 2 @@ -35,8 +35,8 @@ npm version patch \-m "Upgrade to %s for reasons" .fi .RE .P -If the \fBsign\-git\-tag\fR config is set, then the tag will be signed using -the \fB\-s\fR flag to git\. Note that you must have a default GPG key set up +If the \fBsign\-git\-tag\fP config is set, then the tag will be signed using +the \fB\-s\fP flag to git\. Note that you must have a default GPG key set up in your git config for this to work properly\. For example: .P .RS 2 @@ -52,29 +52,29 @@ Enter passphrase: .fi .RE .P -If \fBpreversion\fR, \fBversion\fR, or \fBpostversion\fR are in the \fBscripts\fR property of -the package\.json, they will be executed as part of running \fBnpm version\fR\|\. +If \fBpreversion\fP, \fBversion\fP, or \fBpostversion\fP are in the \fBscripts\fP property of +the package\.json, they will be executed as part of running \fBnpm version\fP\|\. .P The exact order of execution is as follows: .RS 0 .IP 1. 3 Check to make sure the git working directory is clean before we get started\. Your scripts may add files to the commit in future steps\. -This step is skipped if the \fB\-\-force\fR flag is set\. +This step is skipped if the \fB\-\-force\fP flag is set\. .IP 2. 3 -Run the \fBpreversion\fR script\. These scripts have access to the old \fBversion\fR in package\.json\. +Run the \fBpreversion\fP script\. These scripts have access to the old \fBversion\fP in package\.json\. A typical use would be running your full test suite before deploying\. -Any files you want added to the commit should be explicitly added using \fBgit add\fR\|\. +Any files you want added to the commit should be explicitly added using \fBgit add\fP\|\. .IP 3. 3 -Bump \fBversion\fR in \fBpackage\.json\fR as requested (\fBpatch\fR, \fBminor\fR, \fBmajor\fR, etc)\. +Bump \fBversion\fP in \fBpackage\.json\fP as requested (\fBpatch\fP, \fBminor\fP, \fBmajor\fP, etc)\. .IP 4. 3 -Run the \fBversion\fR script\. These scripts have access to the new \fBversion\fR in package\.json +Run the \fBversion\fP script\. These scripts have access to the new \fBversion\fP in package\.json (so they can incorporate it into file headers in generated files for example)\. -Again, scripts should explicitly add generated files to the commit using \fBgit add\fR\|\. +Again, scripts should explicitly add generated files to the commit using \fBgit add\fP\|\. .IP 5. 3 Commit and tag\. .IP 6. 3 -Run the \fBpostversion\fR script\. Use it to clean up the file system or automatically push +Run the \fBpostversion\fP script\. Use it to clean up the file system or automatically push the commit and/or tag\. .RE @@ -91,9 +91,9 @@ Take the following example: .fi .RE .P -This runs all your tests, and proceeds only if they pass\. Then runs your \fBbuild\fR script, and -adds everything in the \fBdist\fR directory to the commit\. After the commit, it pushes the new commit -and tag up to the server, and deletes the \fBbuild/temp\fR directory\. +This runs all your tests, and proceeds only if they pass\. Then runs your \fBbuild\fP script, and +adds everything in the \fBdist\fP directory to the commit\. After the commit, it pushes the new commit +and tag up to the server, and deletes the \fBbuild/temp\fP directory\. .SH CONFIGURATION .SS git\-tag\-version .RS 0 diff --git a/deps/npm/man/man1/npm-view.1 b/deps/npm/man/man1/npm-view.1 index 9c2ca518ee..70f47dc979 100644 --- a/deps/npm/man/man1/npm-view.1 +++ b/deps/npm/man/man1/npm-view.1 @@ -12,9 +12,9 @@ npm v [@<scope>/]<name>[@<version>] [<field>[\.<subfield>]\.\.\.] .SH DESCRIPTION .P This command shows data about a package and prints it to the stream -referenced by the \fBoutfd\fR config, which defaults to stdout\. +referenced by the \fBoutfd\fP config, which defaults to stdout\. .P -To show the package registry entry for the \fBconnect\fR package, you can do +To show the package registry entry for the \fBconnect\fP package, you can do this: .P .RS 2 @@ -26,7 +26,7 @@ npm view connect The default version is "latest" if unspecified\. .P Field names can be specified after the package descriptor\. -For example, to show the dependencies of the \fBronn\fR package at version +For example, to show the dependencies of the \fBronn\fP package at version 0\.3\.5, you could do the following: .P .RS 2 @@ -87,7 +87,7 @@ npm view express contributors\.name contributors\.email .P "Person" fields are shown as a string if they would be shown as an object\. So, for example, this will show the list of npm contributors in -the shortened string format\. (See npm help 5 \fBpackage\.json\fR for more on this\.) +the shortened string format\. (See npm help 5 \fBpackage\.json\fP for more on this\.) .P .RS 2 .nf diff --git a/deps/npm/man/man1/npm-whoami.1 b/deps/npm/man/man1/npm-whoami.1 index 133290c726..d887b35dc0 100644 --- a/deps/npm/man/man1/npm-whoami.1 +++ b/deps/npm/man/man1/npm-whoami.1 @@ -10,7 +10,7 @@ npm whoami .RE .SH DESCRIPTION .P -Print the \fBusername\fR config to standard output\. +Print the \fBusername\fP config to standard output\. .SH SEE ALSO .RS 0 .IP \(bu 2 diff --git a/deps/npm/man/man1/npm.1 b/deps/npm/man/man1/npm.1 index d9ebab559c..5bf8c0954a 100644 --- a/deps/npm/man/man1/npm.1 +++ b/deps/npm/man/man1/npm.1 @@ -10,7 +10,7 @@ npm <command> [args] .RE .SH VERSION .P -2.13.1 +2.13.2 .SH DESCRIPTION .P npm is the package manager for the Node JavaScript platform\. It puts @@ -21,16 +21,16 @@ It is extremely configurable to support a wide variety of use cases\. Most commonly, it is used to publish, discover, install, and develop node programs\. .P -Run \fBnpm help\fR to get a list of available commands\. +Run \fBnpm help\fP to get a list of available commands\. .SH INTRODUCTION .P You probably got npm because you want to install stuff\. .P -Use \fBnpm install blerg\fR to install the latest version of "blerg"\. Check out -npm help \fBnpm\-install\fR for more info\. It can do a lot of stuff\. +Use \fBnpm install blerg\fP to install the latest version of "blerg"\. Check out +npm help \fBnpm\-install\fP for more info\. It can do a lot of stuff\. .P -Use the \fBnpm search\fR command to show everything that's available\. -Use \fBnpm ls\fR to show everything you've installed\. +Use the \fBnpm search\fP command to show everything that's available\. +Use \fBnpm ls\fP to show everything you've installed\. .SH DEPENDENCIES .P If a package references to another package with a git URL, npm depends @@ -48,7 +48,7 @@ the node\-gyp repository \fIhttps://github\.com/TooTallNate/node\-gyp\fR and the node\-gyp Wiki \fIhttps://github\.com/TooTallNate/node\-gyp/wiki\fR\|\. .SH DIRECTORIES .P -See npm help 5 \fBnpm\-folders\fR to learn about where npm puts stuff\. +See npm help 5 \fBnpm\-folders\fP to learn about where npm puts stuff\. .P In particular, npm has two modes of operation: .RS 0 @@ -56,17 +56,17 @@ In particular, npm has two modes of operation: global mode: .br npm installs packages into the install prefix at -\fBprefix/lib/node_modules\fR and bins are installed in \fBprefix/bin\fR\|\. +\fBprefix/lib/node_modules\fP and bins are installed in \fBprefix/bin\fP\|\. .IP \(bu 2 local mode: .br npm installs packages into the current project directory, which defaults to the current working directory\. Packages are installed to -\fB\|\./node_modules\fR, and bins are installed to \fB\|\./node_modules/\.bin\fR\|\. +\fB\|\./node_modules\fP, and bins are installed to \fB\|\./node_modules/\.bin\fP\|\. .RE .P -Local mode is the default\. Use \fB\-\-global\fR or \fB\-g\fR on any command to +Local mode is the default\. Use \fB\-\-global\fP or \fB\-g\fP on any command to operate in global mode instead\. .SH DEVELOPER USAGE .P @@ -75,24 +75,24 @@ following help topics: .RS 0 .IP \(bu 2 json: -Make a package\.json file\. See npm help 5 \fBpackage\.json\fR\|\. +Make a package\.json file\. See npm help 5 \fBpackage\.json\fP\|\. .IP \(bu 2 link: For linking your current working code into Node's path, so that you don't have to reinstall every time you make a change\. Use -\fBnpm link\fR to do this\. +\fBnpm link\fP to do this\. .IP \(bu 2 install: It's a good idea to install things if you don't need the symbolic link\. Especially, installing other peoples code from the registry is done via -\fBnpm install\fR +\fBnpm install\fP .IP \(bu 2 adduser: Create an account or log in\. Credentials are stored in the user config file\. .IP \(bu 2 publish: -Use the \fBnpm publish\fR command to upload your code to the registry\. +Use the \fBnpm publish\fP command to upload your code to the registry\. .RE .SH CONFIGURATION @@ -103,27 +103,27 @@ npm is extremely configurable\. It reads its configuration options from .IP \(bu 2 Command line switches: .br -Set a config with \fB\-\-key val\fR\|\. All keys take a value, even if they +Set a config with \fB\-\-key val\fP\|\. All keys take a value, even if they are booleans (the config parser doesn't know what the options are at the time of parsing\.) If no value is provided, then the option is set -to boolean \fBtrue\fR\|\. +to boolean \fBtrue\fP\|\. .IP \(bu 2 Environment Variables: .br Set any config by prefixing the name in an environment variable with -\fBnpm_config_\fR\|\. For example, \fBexport npm_config_key=val\fR\|\. +\fBnpm_config_\fP\|\. For example, \fBexport npm_config_key=val\fP\|\. .IP \(bu 2 User Configs: .br The file at $HOME/\.npmrc is an ini\-formatted list of configs\. If -present, it is parsed\. If the \fBuserconfig\fR option is set in the cli +present, it is parsed\. If the \fBuserconfig\fP option is set in the cli or env, then that will be used instead\. .IP \(bu 2 Global Configs: .br The file found at \.\./etc/npmrc (from the node executable, by default this resolves to /usr/local/etc/npmrc) will be parsed if it is found\. -If the \fBglobalconfig\fR option is set in the cli, env, or user config, +If the \fBglobalconfig\fP option is set in the cli, env, or user config, then that file is parsed instead\. .IP \(bu 2 Defaults: @@ -133,14 +133,14 @@ lib/utils/config\-defs\.js\. These must not be changed\. .RE .P -See npm help 7 \fBnpm\-config\fR for much much more information\. +See npm help 7 \fBnpm\-config\fP for much much more information\. .SH CONTRIBUTIONS .P Patches welcome! .RS 0 .IP \(bu 2 code: -Read through npm help 7 \fBnpm\-coding\-style\fR if you plan to submit code\. +Read through npm help 7 \fBnpm\-coding\-style\fP if you plan to submit code\. You don't have to agree with it, but you do have to follow it\. .IP \(bu 2 docs: @@ -149,8 +149,8 @@ file in the "doc" folder\. (Don't worry about generating the man page\.) .RE .P -Contributors are listed in npm's \fBpackage\.json\fR file\. You can view them -easily by doing \fBnpm view npm contributors\fR\|\. +Contributors are listed in npm's \fBpackage\.json\fP file\. You can view them +easily by doing \fBnpm view npm contributors\fP\|\. .P If you would like to contribute, but don't know what to work on, check the issues list or ask on the mailing list\. @@ -175,7 +175,7 @@ npm\-@googlegroups\.com .RE .P Be sure to include \fIall\fR of the output from the npm command that didn't work -as expected\. The \fBnpm\-debug\.log\fR file is also helpful to provide\. +as expected\. The \fBnpm\-debug\.log\fP file is also helpful to provide\. .P You can also look for isaacs in #node\.js on irc://irc\.freenode\.net\. He will no doubt tell you to put the output in a gist or email\. |