diff options
Diffstat (limited to 'deps/node/deps/npm/man/man1')
60 files changed, 0 insertions, 5012 deletions
diff --git a/deps/node/deps/npm/man/man1/npm-README.1 b/deps/node/deps/npm/man/man1/npm-README.1 deleted file mode 100644 index d616e80e..00000000 --- a/deps/node/deps/npm/man/man1/npm-README.1 +++ /dev/null @@ -1,175 +0,0 @@ -.TH "NPM" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm\fR \- a JavaScript package manager -.P -Build Status \fIhttps://img\.shields\.io/travis/npm/cli/latest\.svg\fR \fIhttps://travis\-ci\.org/npm/cli\fR -.SH SYNOPSIS -.P -This is just enough info to get you up and running\. -.P -Much more info will be available via \fBnpm help\fP once it's installed\. -.SH IMPORTANT -.P -\fBYou need node v6 or higher to run this program\.\fR -.P -To install an old \fBand unsupported\fR version of npm that works on node v5 -and prior, clone the git repo and dig through the old tags and branches\. -.P -\fBnpm is configured to use npm, Inc\.'s public registry at -https://registry\.npmjs\.org by default\.\fR Use of the npm public registry -is subject to terms of use available at https://www\.npmjs\.com/policies/terms\|\. -.P -You can configure npm to use any compatible registry you -like, and even run your own registry\. Check out the doc on -registries \fIhttps://docs\.npmjs\.com/misc/registry\fR\|\. -.SH Super Easy Install -.P -npm is bundled with node \fIhttps://nodejs\.org/en/download/\fR\|\. -.SS Windows Computers -.P -Get the MSI \fIhttps://nodejs\.org/en/download/\fR\|\. npm is in it\. -.SS Apple Macintosh Computers -.P -Get the pkg \fIhttps://nodejs\.org/en/download/\fR\|\. npm is in it\. -.SS Other Sorts of Unices -.P -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\. -.SH Fancy Install (Unix) -.P -There's a pretty robust install script at -https://www\.npmjs\.com/install\.sh\|\. You can download that and run it\. -.P -Here's an example using curl: -.P -.RS 2 -.nf -curl \-L https://www\.npmjs\.com/install\.sh | sh -.fi -.RE -.SS Slightly Fancier -.P -You can set any npm configuration params with that script: -.P -.RS 2 -.nf -npm_config_prefix=/some/path sh install\.sh -.fi -.RE -.P -Or, you can run it in uber\-debuggery mode: -.P -.RS 2 -.nf -npm_debug=1 sh install\.sh -.fi -.RE -.SS Even Fancier -.P -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 \.\.\.\fP, and then -run npm commands by doing \fBnode bin/npm\-cli\.js <command> <args>\fP\|\. (This is helpful -for testing, or running stuff without actually installing npm itself\.) -.SH Windows Install or Upgrade -.P -Many improvements for Windows users have been made in npm 3 \- you will have a better -experience if you run a recent version of npm\. To upgrade, either use Microsoft's -upgrade tool \fIhttps://github\.com/felixrieseberg/npm\-windows\-upgrade\fR, -download a new version of Node \fIhttps://nodejs\.org/en/download/\fR, -or follow the Windows upgrade instructions in the -Installing/upgrading npm \fIhttps://npm\.community/t/installing\-upgrading\-npm/251/2\fR post\. -.P -If that's not fancy enough for you, then you can fetch the code with -git, and mess with it directly\. -.SH Installing on Cygwin -.P -No\. -.SH Uninstalling -.P -So sad to see you go\. -.P -.RS 2 -.nf -sudo npm uninstall npm \-g -.fi -.RE -.P -Or, if that fails, -.P -.RS 2 -.nf -sudo make uninstall -.fi -.RE -.SH More Severe Uninstalling -.P -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\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\fP script file\. You can run it conveniently like this: -.P -.RS 2 -.nf -npm explore npm \-g \-\- sh scripts/clean\-old\.sh -.fi -.RE -.P -npm uses two configuration files, one for per\-user configs, and another -for global (every\-user) configs\. You can view them by doing: -.P -.RS 2 -.nf -npm config get userconfig # defaults to ~/\.npmrc -npm config get globalconfig # defaults to /usr/local/etc/npmrc -.fi -.RE -.P -Uninstalling npm does not remove configuration files by default\. You -must remove them yourself manually if you want them gone\. Note that -this means that future npm installs will not remember the settings that -you have chosen\. -.SH More Docs -.P -Check out the docs \fIhttps://docs\.npmjs\.com/\fR\|\. -.P -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\|\. -.SH BUGS -.P -When you find issues, please report them: -.RS 0 -.IP \(bu 2 -web: -https://npm\.community/c/bugs - -.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\fP file is also helpful to provide\. -.P -You can also find npm people in \fB#npm\fP on https:// or -on Twitter \fIhttps://twitter\.com/npm_support\fR\|\. Whoever responds will no -doubt tell you to put the output in a gist or email\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help npm -.IP \(bu 2 -npm help help -.IP \(bu 2 -npm help 7 index - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-access.1 b/deps/node/deps/npm/man/man1/npm-access.1 deleted file mode 100644 index db77a409..00000000 --- a/deps/node/deps/npm/man/man1/npm-access.1 +++ /dev/null @@ -1,101 +0,0 @@ -.TH "NPM\-ACCESS" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-access\fR \- Set access level on published packages -.SH SYNOPSIS -.P -.RS 2 -.nf -npm access public [<package>] -npm access restricted [<package>] - -npm access grant <read\-only|read\-write> <scope:team> [<package>] -npm access revoke <scope:team> [<package>] - -npm access 2fa\-required [<package>] -npm access 2fa\-not\-required [<package>] - -npm access ls\-packages [<user>|<scope>|<scope:team>] -npm access ls\-collaborators [<package> [<user>]] -npm access edit [<package>] -.fi -.RE -.SH DESCRIPTION -.P -Used to set access controls on private packages\. -.P -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 -.IP \(bu 2 -public / restricted: -Set a package to be either publicly accessible or restricted\. -.IP \(bu 2 -grant / revoke: -Add or remove the ability of users and teams to have read\-only or read\-write -access to a package\. -.IP \(bu 2 -2fa\-required / 2fa\-not\-required: -Configure whether a package requires that anyone publishing it have two\-factor -authentication enabled on their account\. -.IP \(bu 2 -ls\-packages: -Show all of the packages a user or a team is able to access, along with the -access level, except for read\-only public packages (it won't print the whole -registry listing) -.IP \(bu 2 -ls\-collaborators: -Show all of the access privileges for a package\. Will only show permissions -for packages to which you have at least read access\. If \fB<user>\fP is passed in, -the list is filtered only to teams \fIthat\fR user happens to belong to\. -.IP \(bu 2 -edit: -Set the access privileges for a package at once using \fB$EDITOR\fP\|\. - -.RE -.SH DETAILS -.P -\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\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 -.IP \(bu 2 -You are an owner of an unscoped or scoped package\. -.IP \(bu 2 -You are a member of the team that owns a scope\. -.IP \(bu 2 -You have been given read\-write privileges for a package, either as a member -of a team or directly as an owner\. - -.RE -.P -If you have two\-factor authentication enabled then you'll have to pass in an -otp with \fB\-\-otp\fP when making access changes\. -.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\fP\|\. -.P -Management of teams and team memberships is done with the \fBnpm team\fP command\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -\fBlibnpmaccess\fP \fIhttps://npm\.im/libnpmaccess\fR -.IP \(bu 2 -npm help team -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 7 registry - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-adduser.1 b/deps/node/deps/npm/man/man1/npm-adduser.1 deleted file mode 100644 index a2158576..00000000 --- a/deps/node/deps/npm/man/man1/npm-adduser.1 +++ /dev/null @@ -1,103 +0,0 @@ -.TH "NPM\-ADDUSER" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-adduser\fR \- Add a registry user account -.SH SYNOPSIS -.P -.RS 2 -.nf -npm adduser [\-\-registry=url] [\-\-scope=@orgname] [\-\-always\-auth] [\-\-auth\-type=legacy] - -aliases: login, add\-user -.fi -.RE -.SH DESCRIPTION -.P -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 -To reset your password, go to https://www\.npmjs\.com/forgot -.P -To change your email address, go to https://www\.npmjs\.com/email\-edit -.P -You may use this command multiple times with the same user account to -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\fP is an alias to \fBadduser\fP and behaves exactly the same way\. -.SH CONFIGURATION -.SS registry -.P -Default: https:// -.P -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\. \fBscope\fP defaults -to the scope of the project directory you're currently in, if any\. 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\fP\|\. You can use both at the same time, -e\.g\. -.P -.RS 2 -.nf -npm adduser \-\-registry=http://myregistry\.example\.com \-\-scope=@myco -.fi -.RE -.P -This will set a registry for the given scope and login or create a user for -that registry at the same time\. -.SS always\-auth -.P -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\fP and / or \fB\-\-scope\fP, e\.g\. -.P -.RS 2 -.nf -npm adduser \-\-registry=http://private\-registry\.example\.com \-\-always\-auth -.fi -.RE -.P -This will ensure that all requests to that registry (including for tarballs) -include an authorization header\. This setting may be necessary for use with -private registries where metadata and package tarballs are stored on hosts with -different hostnames\. 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\. -.SS auth\-type -.RS 0 -.IP \(bu 2 -Default: \fB\|'legacy'\fP -.IP \(bu 2 -Type: \fB\|'legacy'\fP, \fB\|'sso'\fP, \fB\|'saml'\fP, \fB\|'oauth'\fP - -.RE -.P -What authentication strategy to use with \fBadduser\fP/\fBlogin\fP\|\. Some npm registries -(for example, npmE) might support alternative auth strategies besides classic -username/password entry in legacy npm\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help owner -.IP \(bu 2 -npm help whoami - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-audit.1 b/deps/node/deps/npm/man/man1/npm-audit.1 deleted file mode 100644 index dee3bb03..00000000 --- a/deps/node/deps/npm/man/man1/npm-audit.1 +++ /dev/null @@ -1,150 +0,0 @@ -.TH "NPM\-AUDIT" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-audit\fR \- Run a security audit -.SH SYNOPSIS -.P -.RS 2 -.nf -npm audit [\-\-json|\-\-parseable] -npm audit fix [\-\-force|\-\-package\-lock\-only|\-\-dry\-run|\-\-production|\-\-only=dev] -.fi -.RE -.SH EXAMPLES -.P -Scan your project for vulnerabilities and automatically install any compatible -updates to vulnerable dependencies: -.P -.RS 2 -.nf -$ npm audit fix -.fi -.RE -.P -Run \fBaudit fix\fP without modifying \fBnode_modules\fP, but still updating the -pkglock: -.P -.RS 2 -.nf -$ npm audit fix \-\-package\-lock\-only -.fi -.RE -.P -Skip updating \fBdevDependencies\fP: -.P -.RS 2 -.nf -$ npm audit fix \-\-only=prod -.fi -.RE -.P -Have \fBaudit fix\fP install semver\-major updates to toplevel dependencies, not just -semver\-compatible ones: -.P -.RS 2 -.nf -$ npm audit fix \-\-force -.fi -.RE -.P -Do a dry run to get an idea of what \fBaudit fix\fP will do, and \fIalso\fR output -install information in JSON format: -.P -.RS 2 -.nf -$ npm audit fix \-\-dry\-run \-\-json -.fi -.RE -.P -Scan your project for vulnerabilities and just show the details, without fixing -anything: -.P -.RS 2 -.nf -$ npm audit -.fi -.RE -.P -Get the detailed audit report in JSON format: -.P -.RS 2 -.nf -$ npm audit \-\-json -.fi -.RE -.P -Get the detailed audit report in plain text result, separated by tab characters, allowing for -future reuse in scripting or command line post processing, like for example, selecting -some of the columns printed: -.P -.RS 2 -.nf -$ npm audit \-\-parseable -.fi -.RE -.P -To parse columns, you can use for example \fBawk\fP, and just print some of them: -.P -.RS 2 -.nf -$ npm audit \-\-parseable | awk \-F $'\\t' '{print $1,$4}' -.fi -.RE -.SH DESCRIPTION -.P -The audit command submits a description of the dependencies configured in -your project to your default registry and asks for a report of known -vulnerabilities\. The report returned includes instructions on how to act on -this information\. -.P -You can also have npm automatically fix the vulnerabilities by running \fBnpm -audit fix\fP\|\. Note that some vulnerabilities cannot be fixed automatically and -will require manual intervention or review\. Also note that since \fBnpm audit fix\fP -runs a full\-fledged \fBnpm install\fP under the hood, all configs that apply to the -installer will also apply to \fBnpm install\fP \-\- so things like \fBnpm audit fix -\-\-package\-lock\-only\fP will work as expected\. -.SH CONTENT SUBMITTED -.RS 0 -.IP \(bu 2 -npm_version -.IP \(bu 2 -node_version -.IP \(bu 2 -platform -.IP \(bu 2 -node_env -.IP \(bu 2 -A scrubbed version of your package\-lock\.json or npm\-shrinkwrap\.json - -.RE -.SS SCRUBBING -.P -In order to ensure that potentially sensitive information is not included in -the audit data bundle, some dependencies may have their names (and sometimes -versions) replaced with opaque non\-reversible identifiers\. It is done for -the following dependency types: -.RS 0 -.IP \(bu 2 -Any module referencing a scope that is configured for a non\-default -registry has its name scrubbed\. (That is, a scope you did a \fBnpm login \-\-scope=@ourscope\fP for\.) -.IP \(bu 2 -All git dependencies have their names and specifiers scrubbed\. -.IP \(bu 2 -All remote tarball dependencies have their names and specifiers scrubbed\. -.IP \(bu 2 -All local directory and tarball dependencies have their names and specifiers scrubbed\. - -.RE -.P -The non\-reversible identifiers are a sha256 of a session\-specific UUID and the -value being replaced, ensuring a consistent value within the payload that is -different between runs\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help 5 package\-locks -.IP \(bu 2 -npm help 7 config - -.RE diff --git a/deps/node/deps/npm/man/man1/npm-bin.1 b/deps/node/deps/npm/man/man1/npm-bin.1 deleted file mode 100644 index edec701b..00000000 --- a/deps/node/deps/npm/man/man1/npm-bin.1 +++ /dev/null @@ -1,30 +0,0 @@ -.TH "NPM\-BIN" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-bin\fR \- Display npm bin folder -.SH SYNOPSIS -.P -.RS 2 -.nf -npm bin [\-g|\-\-global] -.fi -.RE -.SH DESCRIPTION -.P -Print the folder where npm will install executables\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help prefix -.IP \(bu 2 -npm help root -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-bugs.1 b/deps/node/deps/npm/man/man1/npm-bugs.1 deleted file mode 100644 index d34e0987..00000000 --- a/deps/node/deps/npm/man/man1/npm-bugs.1 +++ /dev/null @@ -1,60 +0,0 @@ -.TH "NPM\-BUGS" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-bugs\fR \- Bugs for a package in a web browser maybe -.SH SYNOPSIS -.P -.RS 2 -.nf -npm bugs [<pkgname>] - -aliases: issues -.fi -.RE -.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\fP -config param\. If no 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"\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\fP command to open websites\. -.SS registry -.RS 0 -.IP \(bu 2 -Default: https:// -.IP \(bu 2 -Type: url - -.RE -.P -The base URL of the npm package registry\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help docs -.IP \(bu 2 -npm help view -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 5 package\.json - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-build.1 b/deps/node/deps/npm/man/man1/npm-build.1 deleted file mode 100644 index b4247d95..00000000 --- a/deps/node/deps/npm/man/man1/npm-build.1 +++ /dev/null @@ -1,41 +0,0 @@ -.TH "NPM\-BUILD" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-build\fR \- Build a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm build [<package\-folder>] -.fi -.RE -.RS 0 -.IP \(bu 2 -\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\fP and \fBnpm install\fP\|\. -.P -It should generally be called during installation, but if you need to run it -directly, run: -.P -.RS 2 -.nf -npm run\-script build -.fi -.RE -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help link -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help 5 package\.json - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-bundle.1 b/deps/node/deps/npm/man/man1/npm-bundle.1 deleted file mode 100644 index 2b00e67c..00000000 --- a/deps/node/deps/npm/man/man1/npm-bundle.1 +++ /dev/null @@ -1,17 +0,0 @@ -.TH "NPM\-BUNDLE" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-bundle\fR \- REMOVED -.SH DESCRIPTION -.P -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\fP now to do what \fBnpm bundle\fP used to do\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help install - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-cache.1 b/deps/node/deps/npm/man/man1/npm-cache.1 deleted file mode 100644 index 2dc34810..00000000 --- a/deps/node/deps/npm/man/man1/npm-cache.1 +++ /dev/null @@ -1,96 +0,0 @@ -.TH "NPM\-CACHE" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-cache\fR \- Manipulates packages cache -.SH SYNOPSIS -.P -.RS 2 -.nf -npm cache add <tarball file> -npm cache add <folder> -npm cache add <tarball url> -npm cache add <name>@<version> - -npm cache clean [<path>] -aliases: npm cache clear, npm cache rm - -npm cache verify -.fi -.RE -.SH DESCRIPTION -.P -Used to add, list, or clean the npm cache folder\. -.RS 0 -.IP \(bu 2 -add: -Add the specified package to the local cache\. This command is primarily -intended to be used internally by npm, but it can provide a way to -add data to the local installation cache explicitly\. -.IP \(bu 2 -clean: -Delete all data out of the cache folder\. -.IP \(bu 2 -verify: -Verify the contents of the cache folder, garbage collecting any unneeded data, -and verifying the integrity of the cache index and all cached data\. - -.RE -.SH DETAILS -.P -npm stores cache data in an opaque directory within the configured \fBcache\fP, -named \fB_cacache\fP\|\. This directory is a \fBcacache\fP\-based content\-addressable cache -that stores all http request data as well as other package\-related data\. This -directory is primarily accessed through \fBpacote\fP, the library responsible for -all package fetching as of npm@5\. -.P -All data that passes through the cache is fully verified for integrity on both -insertion and extraction\. Cache corruption will either trigger an error, or -signal to \fBpacote\fP that the data must be refetched, which it will do -automatically\. For this reason, it should never be necessary to clear the cache -for any reason other than reclaiming disk space, thus why \fBclean\fP now requires -\fB\-\-force\fP to run\. -.P -There is currently no method exposed through npm to inspect or directly manage -the contents of this cache\. In order to access it, \fBcacache\fP must be used -directly\. -.P -npm will not remove data by itself: the cache will grow as new packages are -installed\. -.SH A NOTE ABOUT THE CACHE'S DESIGN -.P -The npm cache is strictly a cache: it should not be relied upon as a persistent -and reliable data store for package data\. npm makes no guarantee that a -previously\-cached piece of data will be available later, and will automatically -delete corrupted contents\. The primary guarantee that the cache makes is that, -if it does return data, that data will be exactly the data that was inserted\. -.P -To run an offline verification of existing cache contents, use \fBnpm cache -verify\fP\|\. -.SH CONFIGURATION -.SS cache -.P -Default: \fB~/\.npm\fP on Posix, or \fB%AppData%/npm\-cache\fP on Windows\. -.P -The root cache folder\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help pack -.IP \(bu 2 -https:// -.IP \(bu 2 -https:// - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-ci.1 b/deps/node/deps/npm/man/man1/npm-ci.1 deleted file mode 100644 index b872c004..00000000 --- a/deps/node/deps/npm/man/man1/npm-ci.1 +++ /dev/null @@ -1,77 +0,0 @@ -.TH "NPM\-CI" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-ci\fR \- Install a project with a clean slate -.SH SYNOPSIS -.P -.RS 2 -.nf -npm ci -.fi -.RE -.SH EXAMPLE -.P -Make sure you have a package\-lock and an up\-to\-date install: -.P -.RS 2 -.nf -$ cd \./my/npm/project -$ npm install -added 154 packages in 10s -$ ls | grep package\-lock -.fi -.RE -.P -Run \fBnpm ci\fP in that project -.P -.RS 2 -.nf -$ npm ci -added 154 packages in 5s -.fi -.RE -.P -Configure Travis to build using \fBnpm ci\fP instead of \fBnpm install\fP: -.P -.RS 2 -.nf -# \.travis\.yml -install: -\- npm ci -# keep the npm cache around to speed up installs -cache: - directories: - \- "$HOME/\.npm" -.fi -.RE -.SH DESCRIPTION -.P -This command is similar to npm help \fBnpm\-install\fP, except it's meant to be used in -automated environments such as test platforms, continuous integration, and -deployment \-\- or any situation where you want to make sure you're doing a clean -install of your dependencies\. It can be significantly faster than a regular npm -install by skipping certain user\-oriented features\. It is also more strict than -a regular install, which can help catch errors or inconsistencies caused by the -incrementally\-installed local environments of most npm users\. -.P -In short, the main differences between using \fBnpm install\fP and \fBnpm ci\fP are: -.RS 0 -.IP \(bu 2 -The project \fBmust\fR have an existing \fBpackage\-lock\.json\fP or \fBnpm\-shrinkwrap\.json\fP\|\. -.IP \(bu 2 -If dependencies in the package lock do not match those in \fBpackage\.json\fP, \fBnpm ci\fP will exit with an error, instead of updating the package lock\. -.IP \(bu 2 -\fBnpm ci\fP can only install entire projects at a time: individual dependencies cannot be added with this command\. -.IP \(bu 2 -If a \fBnode_modules\fP is already present, it will be automatically removed before \fBnpm ci\fP begins its install\. -.IP \(bu 2 -It will never write to \fBpackage\.json\fP or any of the package\-locks: installs are essentially frozen\. - -.RE -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help 5 package\-locks - -.RE diff --git a/deps/node/deps/npm/man/man1/npm-completion.1 b/deps/node/deps/npm/man/man1/npm-completion.1 deleted file mode 100644 index 9f424dc2..00000000 --- a/deps/node/deps/npm/man/man1/npm-completion.1 +++ /dev/null @@ -1,43 +0,0 @@ -.TH "NPM\-COMPLETION" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-completion\fR \- Tab Completion for npm -.SH SYNOPSIS -.P -.RS 2 -.nf -source <(npm completion) -.fi -.RE -.SH 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\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 7 developers -.IP \(bu 2 -npm help npm - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-config.1 b/deps/node/deps/npm/man/man1/npm-config.1 deleted file mode 100644 index cc9f9cff..00000000 --- a/deps/node/deps/npm/man/man1/npm-config.1 +++ /dev/null @@ -1,97 +0,0 @@ -.TH "NPM\-CONFIG" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-config\fR \- Manage the npm configuration files -.SH SYNOPSIS -.P -.RS 2 -.nf -npm config set <key> <value> [\-g|\-\-global] -npm config get <key> -npm config delete <key> -npm config list [\-l] [\-\-json] -npm config edit -npm get <key> -npm set <key> <value> [\-g|\-\-global] - -aliases: c -.fi -.RE -.SH DESCRIPTION -.P -npm gets its config settings from the command line, environment -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\fP for a more thorough discussion of the mechanisms -involved\. -.P -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 -Config supports the following sub\-commands: -.SS set -.P -.RS 2 -.nf -npm config set key value -.fi -.RE -.P -Sets the config key to the value\. -.P -If value is omitted, then it sets it to "true"\. -.SS get -.P -.RS 2 -.nf -npm config get key -.fi -.RE -.P -Echo the config value to stdout\. -.SS list -.P -.RS 2 -.nf -npm config list -.fi -.RE -.P -Show all the config settings\. Use \fB\-l\fP to also show defaults\. Use \fB\-\-json\fP -to show the settings in json format\. -.SS delete -.P -.RS 2 -.nf -npm config delete key -.fi -.RE -.P -Deletes the key from all configuration files\. -.SS edit -.P -.RS 2 -.nf -npm config edit -.fi -.RE -.P -Opens the config file in an editor\. Use the \fB\-\-global\fP flag to edit the -global config\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 package\.json -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help npm - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-dedupe.1 b/deps/node/deps/npm/man/man1/npm-dedupe.1 deleted file mode 100644 index 8f221481..00000000 --- a/deps/node/deps/npm/man/man1/npm-dedupe.1 +++ /dev/null @@ -1,71 +0,0 @@ -.TH "NPM\-DEDUPE" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-dedupe\fR \- Reduce duplication -.SH SYNOPSIS -.P -.RS 2 -.nf -npm dedupe -npm ddp - -aliases: find\-dupes, ddp -.fi -.RE -.SH DESCRIPTION -.P -Searches the local package tree and attempts to simplify the overall -structure by moving dependencies further up the tree, where they can -be more effectively shared by multiple dependent packages\. -.P -For example, consider this dependency graph: -.P -.RS 2 -.nf -a -+\-\- b <\-\- depends on c@1\.0\.x -| `\-\- c@1\.0\.3 -`\-\- d <\-\- depends on c@~1\.0\.9 - `\-\- c@1\.0\.10 -.fi -.RE -.P -In this case, npm help \fBnpm\-dedupe\fP will transform the tree to: -.P -.RS 2 -.nf -a -+\-\- b -+\-\- d -`\-\- c@1\.0\.10 -.fi -.RE -.P -Because of the hierarchical nature of node's module lookup, b and d -will both get their dependency met by the single c package at the root -level of the tree\. -.P -The deduplication algorithm walks the tree, moving each dependency as far -up in the tree as possible, even if duplicates are not found\. This will -result in both a flat and deduplicated tree\. -.P -If a suitable version exists at the target location in the tree -already, then it will be left untouched, but the other duplicates will -be deleted\. -.P -Arguments are ignored\. Dedupe always acts on the entire tree\. -.P -Modules -.P -Note that this operation transforms the dependency tree, but will never -result in new modules being installed\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help ls -.IP \(bu 2 -npm help update -.IP \(bu 2 -npm help install - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-deprecate.1 b/deps/node/deps/npm/man/man1/npm-deprecate.1 deleted file mode 100644 index 1cf39ddb..00000000 --- a/deps/node/deps/npm/man/man1/npm-deprecate.1 +++ /dev/null @@ -1,39 +0,0 @@ -.TH "NPM\-DEPRECATE" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-deprecate\fR \- Deprecate a version of a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm deprecate <pkg>[@<version>] <message> -.fi -.RE -.SH DESCRIPTION -.P -This command will update the npm registry entry for a package, providing -a deprecation warning to all who attempt to install it\. -.P -It works on version ranges \fIhttps://semver\.npmjs\.com/\fR as well as specific -versions, so you can do something like this: -.P -.RS 2 -.nf -npm deprecate my\-thing@"< 0\.2\.3" "critical bug fixed in v0\.2\.3" -.fi -.RE -.P -Note that you must be the package owner to deprecate something\. See the -\fBowner\fP and \fBadduser\fP help topics\. -.P -To un\-deprecate a package, specify an empty string (\fB""\fP) for the \fBmessage\fP -argument\. Note that you must use double quotes with no space between them to -format an empty string\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help 7 registry - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-dist-tag.1 b/deps/node/deps/npm/man/man1/npm-dist-tag.1 deleted file mode 100644 index b10e8ce3..00000000 --- a/deps/node/deps/npm/man/man1/npm-dist-tag.1 +++ /dev/null @@ -1,110 +0,0 @@ -.TH "NPM\-DIST\-TAG" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-dist-tag\fR \- Modify package distribution tags -.SH SYNOPSIS -.P -.RS 2 -.nf -npm dist\-tag add <pkg>@<version> [<tag>] -npm dist\-tag rm <pkg> <tag> -npm dist\-tag ls [<pkg>] - -aliases: dist\-tags -.fi -.RE -.SH DESCRIPTION -.P -Add, remove, and enumerate distribution tags on a package: -.RS 0 -.IP \(bu 2 -add: -Tags the specified version of the package with the specified tag, or the -\fB\-\-tag\fP config if not specified\. If you have two\-factor authentication on -auth\-and\-writes then you’ll need to include a one\-time password on the -command line with \fB\-\-otp <one\-time password>\fP\|\. -.IP \(bu 2 -rm: -Clear a tag that is no longer in use from the package\. -.IP \(bu 2 -ls: -Show all of the dist\-tags for a package, defaulting to the package in -the current prefix\. -This is the default action if none is specified\. - -.RE -.P -A tag can be used when installing packages as a reference to a version instead -of using a specific version number: -.P -.RS 2 -.nf -npm install <name>@<tag> -.fi -.RE -.P -When installing dependencies, a preferred tagged version may be specified: -.P -.RS 2 -.nf -npm install \-\-tag <tag> -.fi -.RE -.P -This also applies to \fBnpm dedupe\fP\|\. -.P -Publishing a package sets the \fBlatest\fP tag to the published version unless the -\fB\-\-tag\fP option is used\. For example, \fBnpm publish \-\-tag=beta\fP\|\. -.P -By default, \fBnpm install <pkg>\fP (without any \fB@<version>\fP or \fB@<tag>\fP -specifier) installs the \fBlatest\fP tag\. -.SH PURPOSE -.P -Tags can be used to provide an alias instead of version numbers\. -.P -For example, a project might choose to have multiple streams of development -and use a different tag for each stream, -e\.g\., \fBstable\fP, \fBbeta\fP, \fBdev\fP, \fBcanary\fP\|\. -.P -By default, the \fBlatest\fP tag is used by npm to identify the current version of -a package, and \fBnpm install <pkg>\fP (without any \fB@<version>\fP or \fB@<tag>\fP -specifier) installs the \fBlatest\fP tag\. Typically, projects only use the \fBlatest\fP -tag for stable release versions, and use other tags for unstable versions such -as prereleases\. -.P -The \fBnext\fP tag is used by some projects to identify the upcoming version\. -.P -By default, other than \fBlatest\fP, no tag has any special significance to npm -itself\. -.SH CAVEATS -.P -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>\fP vs \fBnpm install <pkg>@<tag>\fP\|\. -.P -Tags that can be interpreted as valid semver ranges will be 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\fP\|\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help dedupe -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-docs.1 b/deps/node/deps/npm/man/man1/npm-docs.1 deleted file mode 100644 index 6d7ac688..00000000 --- a/deps/node/deps/npm/man/man1/npm-docs.1 +++ /dev/null @@ -1,60 +0,0 @@ -.TH "NPM\-DOCS" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-docs\fR \- Docs for a package in a web browser maybe -.SH SYNOPSIS -.P -.RS 2 -.nf -npm docs [<pkgname> [<pkgname> \.\.\.]] -npm docs \. -npm home [<pkgname> [<pkgname> \.\.\.]] -npm home \. -.fi -.RE -.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\fP -config param\. You can pass multiple package names at once\. If no -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"\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\fP command to open websites\. -.SS registry -.RS 0 -.IP \(bu 2 -Default: https:// -.IP \(bu 2 -Type: url - -.RE -.P -The base URL of the npm package registry\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help view -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 5 package\.json - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-doctor.1 b/deps/node/deps/npm/man/man1/npm-doctor.1 deleted file mode 100644 index aa55d151..00000000 --- a/deps/node/deps/npm/man/man1/npm-doctor.1 +++ /dev/null @@ -1,113 +0,0 @@ -.TH "NPM\-DOCTOR" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-doctor\fR \- Check your environments -.SH SYNOPSIS -.P -.RS 2 -.nf -npm doctor -.fi -.RE -.SH DESCRIPTION -.P -\fBnpm doctor\fP runs a set of checks to ensure that your npm installation has -what it needs to manage your JavaScript packages\. npm is mostly a standalone tool, but it does -have some basic requirements that must be met: -.RS 0 -.IP \(bu 2 -Node\.js and git must be executable by npm\. -.IP \(bu 2 -The primary npm registry, \fBregistry\.npmjs\.com\fP, or another service that uses -the registry API, is available\. -.IP \(bu 2 -The directories that npm uses, \fBnode_modules\fP (both locally and globally), -exist and can be written by the current user\. -.IP \(bu 2 -The npm cache exists, and the package tarballs within it aren't corrupt\. - -.RE -.P -Without all of these working properly, npm may not work properly\. Many issues -are often attributable to things that are outside npm's code base, so \fBnpm -doctor\fP confirms that the npm installation is in a good state\. -.P -Also, in addition to this, there are also very many issue reports due to using -old versions of npm\. Since npm is constantly improving, running \fBnpm@latest\fP is -better than an old version\. -.P -\fBnpm doctor\fP verifies the following items in your environment, and if there are -any recommended changes, it will display them\. -.SS \fBnpm ping\fP -.P -By default, npm installs from the primary npm registry, \fBregistry\.npmjs\.org\fP\|\. -\fBnpm doctor\fP hits a special ping endpoint within the registry\. This can also be -checked with \fBnpm ping\fP\|\. If this check fails, you may be using a proxy that -needs to be configured, or may need to talk to your IT staff to get access over -HTTPS to \fBregistry\.npmjs\.org\fP\|\. -.P -This check is done against whichever registry you've configured (you can see -what that is by running \fBnpm config get registry\fP), and if you're using a -private registry that doesn't support the \fB/whoami\fP endpoint supported by the -primary registry, this check may fail\. -.SS \fBnpm \-v\fP -.P -While Node\.js may come bundled with a particular version of npm, it's the -policy of the CLI team that we recommend all users run \fBnpm@latest\fP if they -can\. As the CLI is maintained by a small team of contributors, there are only -resources for a single line of development, so npm's own long\-term support -releases typically only receive critical security and regression fixes\. The -team believes that the latest tested version of npm is almost always likely to -be the most functional and defect\-free version of npm\. -.SS \fBnode \-v\fP -.P -For most users, in most circumstances, the best version of Node will be the -latest long\-term support (LTS) release\. Those of you who want access to new -ECMAscript features or bleeding\-edge changes to Node's standard library may be -running a newer version, and some of you may be required to run an older -version of Node because of enterprise change control policies\. That's OK! But -in general, the npm team recommends that most users run Node\.js LTS\. -.SS \fBnpm config get registry\fP -.P -Some of you may be installing from private package registries for your project -or company\. That's great! Others of you may be following tutorials or -StackOverflow questions in an effort to troubleshoot problems you may be -having\. Sometimes, this may entail changing the registry you're pointing at\. -This part of \fBnpm doctor\fP just lets you, and maybe whoever's helping you with -support, know that you're not using the default registry\. -.SS \fBwhich git\fP -.P -While it's documented in the README, it may not be obvious that npm needs Git -installed to do many of the things that it does\. Also, in some cases -– especially on Windows – you may have Git set up in such a way that it's not -accessible via your \fBPATH\fP so that npm can find it\. This check ensures that Git -is available\. -.SS Permissions checks -.RS 0 -.IP \(bu 2 -Your cache must be readable and writable by the user running npm\. -.IP \(bu 2 -Global package binaries must be writable by the user running npm\. -.IP \(bu 2 -Your local \fBnode_modules\fP path, if you're running \fBnpm doctor\fP with a project -directory, must be readable and writable by the user running npm\. - -.RE -.SS Validate the checksums of cached packages -.P -When an npm package is published, the publishing process generates a checksum -that npm uses at install time to verify that the package didn't get corrupted -in transit\. \fBnpm doctor\fP uses these checksums to validate the package tarballs -in your local cache (you can see where that cache is located with \fBnpm config -get cache\fP, and see what's in that cache with \fBnpm cache ls\fP – probably more -than you were expecting!)\. In the event that there are corrupt packages in your -cache, you should probably run \fBnpm cache clean\fP and reset the cache\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help bugs -.IP \(bu 2 -npm help help -.IP \(bu 2 -npm help ping - -.RE diff --git a/deps/node/deps/npm/man/man1/npm-edit.1 b/deps/node/deps/npm/man/man1/npm-edit.1 deleted file mode 100644 index 9146f3b7..00000000 --- a/deps/node/deps/npm/man/man1/npm-edit.1 +++ /dev/null @@ -1,52 +0,0 @@ -.TH "NPM\-EDIT" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-edit\fR \- Edit an installed package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm edit <pkg>[/<subpkg>\.\.\.] -.fi -.RE -.SH DESCRIPTION -.P -Selects a (sub)dependency in the current -working directory and opens the package folder in the default editor -(or whatever you've 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\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\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\fP or \fBnpm config edit\fP\|\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help explore -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-explore.1 b/deps/node/deps/npm/man/man1/npm-explore.1 deleted file mode 100644 index 89df7251..00000000 --- a/deps/node/deps/npm/man/man1/npm-explore.1 +++ /dev/null @@ -1,55 +0,0 @@ -.TH "NPM\-EXPLORE" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-explore\fR \- Browse an installed package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm explore <pkg> [ \-\- <command>] -.fi -.RE -.SH DESCRIPTION -.P -Spawn a subshell in the directory of the installed package specified\. -.P -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\fP folder: -.P -.RS 2 -.nf -npm explore some\-dependency \-\- git pull origin master -.fi -.RE -.P -Note that the package is \fInot\fR automatically rebuilt afterwards, so be -sure to use \fBnpm rebuild <pkg>\fP if you make any changes\. -.SH CONFIGURATION -.SS shell -.RS 0 -.IP \(bu 2 -Default: SHELL environment variable, or "bash" on Posix, or "cmd" on -Windows -.IP \(bu 2 -Type: path - -.RE -.P -The shell to run for the \fBnpm explore\fP command\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help edit -.IP \(bu 2 -npm help rebuild -.IP \(bu 2 -npm help build -.IP \(bu 2 -npm help install - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-help-search.1 b/deps/node/deps/npm/man/man1/npm-help-search.1 deleted file mode 100644 index e298e8d9..00000000 --- a/deps/node/deps/npm/man/man1/npm-help-search.1 +++ /dev/null @@ -1,43 +0,0 @@ -.TH "NPM\-HELP\-SEARCH" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-help-search\fR \- Search npm help documentation -.SH SYNOPSIS -.P -.RS 2 -.nf -npm help\-search <text> -.fi -.RE -.SH DESCRIPTION -.P -This command will search the npm markdown documentation files for the -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\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 -.RS 0 -.IP \(bu 2 -Type: Boolean -.IP \(bu 2 -Default: false - -.RE -.P -If true, the "long" flag will cause help\-search to output context around -where the terms were found in the documentation\. -.P -If false, then help\-search will just list out the help topics found\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help npm -.IP \(bu 2 -npm help help - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-help.1 b/deps/node/deps/npm/man/man1/npm-help.1 deleted file mode 100644 index c07f2859..00000000 --- a/deps/node/deps/npm/man/man1/npm-help.1 +++ /dev/null @@ -1,54 +0,0 @@ -.TH "NPM\-HELP" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-help\fR \- Get help on npm -.SH SYNOPSIS -.P -.RS 2 -.nf -npm help <term> [<terms\.\.>] -.fi -.RE -.SH DESCRIPTION -.P -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\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 -.RS 0 -.IP \(bu 2 -Default: "man" on Posix, "browser" on Windows -.IP \(bu 2 -Type: path - -.RE -.P -The program to use to view help content\. -.P -Set to \fB"browser"\fP to view html help content in the default web browser\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help npm -.IP \(bu 2 -README -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 5 package\.json -.IP \(bu 2 -npm help help\-search -.IP \(bu 2 -npm help 7 index - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-hook.1 b/deps/node/deps/npm/man/man1/npm-hook.1 deleted file mode 100644 index 47b17516..00000000 --- a/deps/node/deps/npm/man/man1/npm-hook.1 +++ /dev/null @@ -1,97 +0,0 @@ -.TH "NPM\-HOOK" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-hook\fR \- Manage registry hooks -.SH SYNOPSIS -.P -.RS 2 -.nf -npm hook ls [pkg] -npm hook add <entity> <url> <secret> -npm hook update <id> <url> [secret] -npm hook rm <id> -.fi -.RE -.SH EXAMPLE -.P -Add a hook to watch a package for changes: -.P -.RS 2 -.nf -$ npm hook add lodash https://example\.com/ my\-shared\-secret -.fi -.RE -.P -Add a hook to watch packages belonging to the user \fBsubstack\fP: -.P -.RS 2 -.nf -$ npm hook add ~substack https://example\.com/ my\-shared\-secret -.fi -.RE -.P -Add a hook to watch packages in the scope \fB@npm\fP -.P -.RS 2 -.nf -$ npm hook add @npm https://example\.com/ my\-shared\-secret -.fi -.RE -.P -List all your active hooks: -.P -.RS 2 -.nf -$ npm hook ls -.fi -.RE -.P -List your active hooks for the \fBlodash\fP package: -.P -.RS 2 -.nf -$ npm hook ls lodash -.fi -.RE -.P -Update an existing hook's url: -.P -.RS 2 -.nf -$ npm hook update id\-deadbeef https://my\-new\-website\.here/ -.fi -.RE -.P -Remove a hook: -.P -.RS 2 -.nf -$ npm hook rm id\-deadbeef -.fi -.RE -.SH DESCRIPTION -.P -Allows you to manage npm -hooks \fIhttps://blog\.npmjs\.org/post/145260155635/introducing\-hooks\-get\-notifications\-of\-npm\fR, -including adding, removing, listing, and updating\. -.P -Hooks allow you to configure URL endpoints that will be notified whenever a -change happens to any of the supported entity types\. Three different types of -entities can be watched by hooks: packages, owners, and scopes\. -.P -To create a package hook, simply reference the package name\. -.P -To create an owner hook, prefix the owner name with \fB~\fP (as in, \fB~youruser\fP)\. -.P -To create a scope hook, prefix the scope name with \fB@\fP (as in, \fB@yourscope\fP)\. -.P -The hook \fBid\fP used by \fBupdate\fP and \fBrm\fP are the IDs listed in \fBnpm hook ls\fP for -that particular hook\. -.P -The shared secret will be sent along to the URL endpoint so you can verify the -request came from your own configured hook\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -"Introducing Hooks" blog post \fIhttps://blog\.npmjs\.org/post/145260155635/introducing\-hooks\-get\-notifications\-of\-npm\fR - -.RE diff --git a/deps/node/deps/npm/man/man1/npm-init.1 b/deps/node/deps/npm/man/man1/npm-init.1 deleted file mode 100644 index 988126a3..00000000 --- a/deps/node/deps/npm/man/man1/npm-init.1 +++ /dev/null @@ -1,91 +0,0 @@ -.TH "NPM\-INIT" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-init\fR \- create a package\.json file -.SH SYNOPSIS -.P -.RS 2 -.nf -npm init [\-\-force|\-f|\-\-yes|\-y|\-\-scope] -npm init <@scope> (same as `npx <@scope>/create`) -npm init [<@scope>/]<name> (same as `npx [<@scope>/]create\-<name>`) -.fi -.RE -.SH EXAMPLES -.P -Create a new React\-based project using \fBcreate\-react\-app\fP \fIhttps://npm\.im/create\-react\-app\fR: -.P -.RS 2 -.nf -$ npm init react\-app \./my\-react\-app -.fi -.RE -.P -Create a new \fBesm\fP\-compatible package using \fBcreate\-esm\fP \fIhttps://npm\.im/create\-esm\fR: -.P -.RS 2 -.nf -$ mkdir my\-esm\-lib && cd my\-esm\-lib -$ npm init esm \-\-yes -.fi -.RE -.P -Generate a plain old package\.json using legacy init: -.P -.RS 2 -.nf -$ mkdir my\-npm\-pkg && cd my\-npm\-pkg -$ git init -$ npm init -.fi -.RE -.P -Generate it without having it ask any questions: -.P -.RS 2 -.nf -$ npm init \-y -.fi -.RE -.SH DESCRIPTION -.P -\fBnpm init <initializer>\fP can be used to set up a new or existing npm package\. -.P -\fBinitializer\fP in this case is an npm package named \fBcreate\-<initializer>\fP, which -will be installed by npm help \fBnpx\fP \fIhttps://npm\.im/npx\fR, and then have its main bin -executed \-\- presumably creating or updating \fBpackage\.json\fP and running any other -initialization\-related operations\. -.P -The init command is transformed to a corresponding \fBnpx\fP operation as follows: -.RS 0 -.IP \(bu 2 -\fBnpm init foo\fP \-> \fBnpx create\-foo\fP -.IP \(bu 2 -\fBnpm init @usr/foo\fP \-> \fBnpx @usr/create\-foo\fP -.IP \(bu 2 -\fBnpm init @usr\fP \-> \fBnpx @usr/create\fP - -.RE -.P -Any additional options will be passed directly to the command, so \fBnpm init foo -\-\-hello\fP will map to \fBnpx create\-foo \-\-hello\fP\|\. -.P -If the initializer is omitted (by just calling \fBnpm init\fP), init will fall back -to legacy init behavior\. It will ask you a bunch of questions, and then write a -package\.json for you\. It will attempt to make reasonable guesses based on -existing fields, dependencies, and options selected\. It is strictly additive, so -it will keep any fields and values that were already set\. You can also use -\fB\-y\fP/\fB\-\-yes\fP to skip the questionnaire altogether\. If you pass \fB\-\-scope\fP, it -will create a scoped package\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -https://github\.com/isaacs/init\-package\-json -.IP \(bu 2 -npm help 5 package\.json -.IP \(bu 2 -npm help version -.IP \(bu 2 -npm help 7 scope - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-install-ci-test.1 b/deps/node/deps/npm/man/man1/npm-install-ci-test.1 deleted file mode 100644 index 6cdda35e..00000000 --- a/deps/node/deps/npm/man/man1/npm-install-ci-test.1 +++ /dev/null @@ -1,23 +0,0 @@ -.TH "NPM" "" "January 2019" "" "" -.SH "NAME" -\fBnpm\fR -.SH SYNOPSIS -.P -.RS 2 -.nf -npm install\-ci\-test - -alias: npm cit -.fi -.RE -.SH DESCRIPTION -.P -This command runs an \fBnpm ci\fP followed immediately by an \fBnpm test\fP\|\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help ci -.IP \(bu 2 -npm help test - -.RE diff --git a/deps/node/deps/npm/man/man1/npm-install-test.1 b/deps/node/deps/npm/man/man1/npm-install-test.1 deleted file mode 100644 index ae8d5223..00000000 --- a/deps/node/deps/npm/man/man1/npm-install-test.1 +++ /dev/null @@ -1,33 +0,0 @@ -.TH "NPM" "" "January 2019" "" "" -.SH "NAME" -\fBnpm\fR -.SH SYNOPSIS -.P -.RS 2 -.nf -npm install\-test (with no args, in package dir) -npm install\-test [<@scope>/]<name> -npm install\-test [<@scope>/]<name>@<tag> -npm install\-test [<@scope>/]<name>@<version> -npm install\-test [<@scope>/]<name>@<version range> -npm install\-test <tarball file> -npm install\-test <tarball url> -npm install\-test <folder> - -alias: npm it -common options: [\-\-save|\-\-save\-dev|\-\-save\-optional] [\-\-save\-exact] [\-\-dry\-run] -.fi -.RE -.SH DESCRIPTION -.P -This command runs an \fBnpm install\fP followed immediately by an \fBnpm test\fP\|\. It -takes exactly the same arguments as \fBnpm install\fP\|\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help test - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-install.1 b/deps/node/deps/npm/man/man1/npm-install.1 deleted file mode 100644 index f2cdfeda..00000000 --- a/deps/node/deps/npm/man/man1/npm-install.1 +++ /dev/null @@ -1,545 +0,0 @@ -.TH "NPM\-INSTALL" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-install\fR \- Install a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm install (with no args, in package dir) -npm install [<@scope>/]<name> -npm install [<@scope>/]<name>@<tag> -npm install [<@scope>/]<name>@<version> -npm install [<@scope>/]<name>@<version range> -npm install <git\-host>:<git\-user>/<repo\-name> -npm install <git repo url> -npm install <tarball file> -npm install <tarball url> -npm install <folder> - -alias: npm i -common options: [\-P|\-\-save\-prod|\-D|\-\-save\-dev|\-O|\-\-save\-optional] [\-E|\-\-save\-exact] [\-B|\-\-save\-bundle] [\-\-no\-save] [\-\-dry\-run] -.fi -.RE -.SH DESCRIPTION -.P -This command installs a package, and any packages that it depends on\. If the -package has a package\-lock or shrinkwrap file, the installation of dependencies -will be driven by that, with an \fBnpm\-shrinkwrap\.json\fP taking precedence if both -files exist\. See npm help 5 package\-lock\.json and npm help shrinkwrap\. -.P -A \fBpackage\fP is: -.RS 0 -.IP \(bu 2 -a) a folder containing a program described by a npm help 5 \fBpackage\.json\fP file -.IP \(bu 2 -b) a gzipped tarball containing (a) -.IP \(bu 2 -c) a url that resolves to (b) -.IP \(bu 2 -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>\fP (see npm help \fBnpm\-dist\-tag\fP) that points to (d) -.IP \(bu 2 -f) a \fB<name>\fP that has a "latest" tag satisfying (e) -.IP \(bu 2 -g) a \fB<git remote url>\fP that resolves to (a) - -.RE -.P -Even if you never publish your package, you can still get a lot of -benefits of using npm if you just want to write a node program (a), and -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\fP (in package directory, no arguments): - Install the dependencies in the local node_modules folder\. - 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\fP will install all modules listed as dependencies - in npm help 5 \fBpackage\.json\fP\|\. - 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\|\. -.QP -NOTE: The \fB\-\-production\fP flag has no particular meaning when adding a - dependency to a project\. - -. -.IP \(bu 2 -\fBnpm install <folder>\fP: - Install the package in the directory as a symlink in the current project\. - Its dependencies will be installed before it's linked\. If \fB<folder>\fP sits - inside the root of your project, its dependencies may be hoisted to the - toplevel \fBnode_modules\fP as they would for other types of dependencies\. -.IP \(bu 2 -\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\fP\|\. - Tarball requirements: -.RS 0 -.IP \(bu 2 -The filename \fImust\fR use \fB\|\.tar\fP, \fB\|\.tar\.gz\fP, or \fB\|\.tgz\fP as -the extension\. -.IP \(bu 2 -The package contents should reside in a subfolder inside the tarball (usually it is called \fBpackage/\fP)\. npm strips one directory layer when installing the package (an equivalent of \fBtar x \-\-strip\-components=1\fP is run)\. -.IP \(bu 2 -The package must contain a \fBpackage\.json\fP file with \fBname\fP and \fBversion\fP properties\. -Example: -.P -.RS 2 -.nf -npm install \./package\.tgz -.fi -.RE - -.RE -.IP \(bu 2 -\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: -.P -.RS 2 -.nf - npm install https://github\.com/indexzero/forever/tarball/v0\.5\.6 -.fi -.RE -.IP \(bu 2 -\fBnpm install [<@scope>/]<name>\fP: - Do a \fB<name>@<tag>\fP install, where \fB<tag>\fP is the "tag" config\. (See - npm help 7 \fBnpm\-config\fP\|\. The config's default value is \fBlatest\fP\|\.) - In most cases, this will install the version of the modules tagged as - \fBlatest\fP on the npm registry\. - Example: -.P -.RS 2 -.nf - npm install sax -.fi -.RE - \fBnpm install\fP saves any specified packages into \fBdependencies\fP by default\. - Additionally, you can control where and how they get saved with some - additional flags: -.RS 0 -.IP \(bu 2 -\fB\-P, \-\-save\-prod\fP: Package will appear in your \fBdependencies\fP\|\. This is the -.P -.RS 2 -.nf - default unless `\-D` or `\-O` are present\. -.fi -.RE -.IP \(bu 2 -\fB\-D, \-\-save\-dev\fP: Package will appear in your \fBdevDependencies\fP\|\. -.IP \(bu 2 -\fB\-O, \-\-save\-optional\fP: Package will appear in your \fBoptionalDependencies\fP\|\. -.IP \(bu 2 -\fB\-\-no\-save\fP: Prevents saving to \fBdependencies\fP\|\. -When using any of the above options to save dependencies to your -package\.json, there are two additional, optional flags: -.IP \(bu 2 -\fB\-E, \-\-save\-exact\fP: Saved dependencies will be configured with an -exact version rather than using npm's default semver range -operator\. -.IP \(bu 2 -\fB\-B, \-\-save\-bundle\fP: Saved dependencies will also be added to your \fBbundleDependencies\fP list\. -Further, if you have an \fBnpm\-shrinkwrap\.json\fP or \fBpackage\-lock\.json\fP then it -will be updated as well\. -\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\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\. -Examples: -.P -.RS 2 -.nf -npm install sax -npm install githubname/reponame -npm install @myorg/privatepackage -npm install node\-tap \-\-save\-dev -npm install dtrace\-provider \-\-save\-optional -npm install readable\-stream \-\-save\-exact -npm install ansi\-regex \-\-save\-bundle -.fi -.RE - -.RE - -.RE -.P -.RS 2 -.nf -**Note**: If there is a file or folder named `<name>` in the current -working directory, then it will try to install that, and only try to -fetch the package by name if it is not valid\. -.fi -.RE -.RS 0 -.IP \(bu 2 -\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\. - Example: -.P -.RS 2 -.nf - npm install sax@latest - npm install @myorg/mypackage@latest -.fi -.RE -.IP \(bu 2 -\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: -.P -.RS 2 -.nf - npm install sax@0\.1\.1 - npm install @myorg/privatepackage@1\.5\.0 -.fi -.RE -.IP \(bu 2 -\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\fP\|\. - Note that most version ranges must be put in quotes so that your shell will - treat it as a single argument\. - Example: -.P -.RS 2 -.nf - npm install sax@">=0\.1\.0 <0\.2\.0" - npm install @myorg/privatepackage@">=0\.1\.0 <0\.2\.0" -.fi -.RE -.IP \(bu 2 -\fBnpm install <git remote url>\fP: - Installs the package from the hosted git provider, cloning it with \fBgit\fP\|\. - For a full git remote url, only that URL will be attempted\. -.P -.RS 2 -.nf - <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit\-ish> | #semver:<semver>] -.fi -.RE - \fB<protocol>\fP is one of \fBgit\fP, \fBgit+ssh\fP, \fBgit+http\fP, \fBgit+https\fP, or - \fBgit+file\fP\|\. - If \fB#<commit\-ish>\fP is provided, it will be used to clone exactly that - commit\. If the commit\-ish has the format \fB#semver:<semver>\fP, \fB<semver>\fP can - be any valid semver range or exact version, and npm will look for any tags - or refs matching that range in the remote repository, much as it would for a - registry dependency\. If neither \fB#<commit\-ish>\fP or \fB#semver:<semver>\fP is - specified, then the default branch of the repository is used\. - If the repository makes use of submodules, those submodules will be cloned - as well\. - If the package being installed contains a \fBprepare\fP script, its - \fBdependencies\fP and \fBdevDependencies\fP will be installed, and the prepare - script will be run, before the package is packaged and installed\. - 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\fP -.IP \(bu 2 -\fBGIT_EXEC_PATH\fP -.IP \(bu 2 -\fBGIT_PROXY_COMMAND\fP -.IP \(bu 2 -\fBGIT_SSH\fP -.IP \(bu 2 -\fBGIT_SSH_COMMAND\fP -.IP \(bu 2 -\fBGIT_SSL_CAINFO\fP -.IP \(bu 2 -\fBGIT_SSL_NO_VERIFY\fP -See the git man page for details\. -Examples: -.P -.RS 2 -.nf -npm install git+ssh://git@github\.com:npm/cli\.git#v1\.0\.27 -npm install git+ssh://git@github\.com:npm/cli#semver:^5\.0 -npm install git+https://isaacs@github\.com/npm/cli\.git -npm install git://github\.com/npm/cli\.git#v1\.0\.27 -GIT_SSH_COMMAND='ssh \-i ~/\.ssh/custom_ident' npm install git+ssh://git@github\.com:npm/cli\.git -.fi -.RE - -.RE -.IP \(bu 2 -\fBnpm install <githubname>/<githubrepo>[#<commit\-ish>]\fP: -.IP \(bu 2 -\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 \fB#<commit\-ish>\fP is provided, it will be used to clone exactly that - commit\. If the commit\-ish has the format \fB#semver:<semver>\fP, \fB<semver>\fP can - be any valid semver range or exact version, and npm will look for any tags - or refs matching that range in the remote repository, much as it would for a - registry dependency\. If neither \fB#<commit\-ish>\fP or \fB#semver:<semver>\fP is - specified, then \fBmaster\fP is used\. - As with regular git dependencies, \fBdependencies\fP and \fBdevDependencies\fP will - be installed if the package has a \fBprepare\fP script, before the package is - done installing\. - Examples: -.P -.RS 2 -.nf - npm install mygithubuser/myproject - npm install github:mygithubuser/myproject -.fi -.RE -.IP \(bu 2 -\fBnpm install gist:[<githubname>/]<gistID>[#<commit\-ish>|#semver:<semver>]\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\|\. - As with regular git dependencies, \fBdependencies\fP and \fBdevDependencies\fP will - be installed if the package has a \fBprepare\fP script, before the package is - done installing\. - Example: -.P -.RS 2 -.nf - npm install gist:101a11beef -.fi -.RE -.IP \(bu 2 -\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 \fB#<commit\-ish>\fP is provided, it will be used to clone exactly that - commit\. If the commit\-ish has the format \fB#semver:<semver>\fP, \fB<semver>\fP can - be any valid semver range or exact version, and npm will look for any tags - or refs matching that range in the remote repository, much as it would for a - registry dependency\. If neither \fB#<commit\-ish>\fP or \fB#semver:<semver>\fP is - specified, then \fBmaster\fP is used\. - As with regular git dependencies, \fBdependencies\fP and \fBdevDependencies\fP will - be installed if the package has a \fBprepare\fP script, before the package is - done installing\. - Example: -.P -.RS 2 -.nf - npm install bitbucket:mybitbucketuser/myproject -.fi -.RE -.IP \(bu 2 -\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 \fB#<commit\-ish>\fP is provided, it will be used to clone exactly that - commit\. If the commit\-ish has the format \fB#semver:<semver>\fP, \fB<semver>\fP can - be any valid semver range or exact version, and npm will look for any tags - or refs matching that range in the remote repository, much as it would for a - registry dependency\. If neither \fB#<commit\-ish>\fP or \fB#semver:<semver>\fP is - specified, then \fBmaster\fP is used\. - As with regular git dependencies, \fBdependencies\fP and \fBdevDependencies\fP will - be installed if the package has a \fBprepare\fP script, before the package is - done installing\. - Example: -.P -.RS 2 -.nf - npm install gitlab:mygitlabuser/myproject - npm install gitlab:myusr/myproj#semver:^5\.0 -.fi -.RE - -.RE -.P -You may combine multiple arguments, and even multiple types of arguments\. -For example: -.P -.RS 2 -.nf -npm install sax@">=0\.1\.0 <0\.2\.0" bench supervisor -.fi -.RE -.P -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\-\-dry\-run\fP argument will report in the usual way what the install would -have done without actually installing anything\. -.P -The \fB\-\-package\-lock\-only\fP argument will only update the \fBpackage\-lock\.json\fP, -instead of checking \fBnode_modules\fP and downloading dependencies\. -.P -The \fB\-f\fP or \fB\-\-force\fP argument will force npm to fetch remote resources even if a -local copy exists on disk\. -.P -.RS 2 -.nf -npm install sax \-\-force -.fi -.RE -.P -The \fB\-g\fP or \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\-\-global\-style\fP argument will cause npm to install the package into -your local \fBnode_modules\fP folder with the same layout it uses with the -global \fBnode_modules\fP folder\. Only your direct dependencies will show in -\fBnode_modules\fP and everything they depend on will be flattened in their -\fBnode_modules\fP folders\. This obviously will eliminate some deduping\. -.P -The \fB\-\-ignore\-scripts\fP argument will cause npm to not execute any -scripts defined in the package\.json\. See npm help 7 \fBnpm\-scripts\fP\|\. -.P -The \fB\-\-legacy\-bundling\fP argument will cause npm to install the package such -that versions of npm prior to 1\.4, such as the one included with node 0\.8, -can install the package\. This eliminates all automatic deduping\. -.P -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\fP argument will prevent npm from creating symlinks for -any binaries the package might contain\. -.P -The \fB\-\-no\-optional\fP argument will prevent optional dependencies from -being installed\. -.P -The \fB\-\-no\-shrinkwrap\fP argument, which will ignore an available -package lock or shrinkwrap file and use the package\.json instead\. -.P -The \fB\-\-no\-package\-lock\fP argument will prevent npm from creating a -\fBpackage\-lock\.json\fP file\. When running with package\-lock's disabled npm -will not automatically prune your node modules when installing\. -.P -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 -The \fB\-\-only={prod[uction]|dev[elopment]}\fP argument will cause either only -\fBdevDependencies\fP or only non\-\fBdevDependencies\fP to be installed regardless of the \fBNODE_ENV\fP\|\. -.P -The \fB\-\-no\-audit\fP argument can be used to disable sending of audit reports to -the configured registries\. See npm help \fBnpm\-audit\fP for details on what is sent\. -.P -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 -To install a package, npm uses the following algorithm: -.P -.RS 2 -.nf -load the existing node_modules tree from disk -clone the tree -fetch the package\.json and assorted metadata and add it to the clone -walk the clone and add any missing dependencies - dependencies will be added as close to the top as is possible - without breaking any other modules -compare the original tree with the cloned tree and make a list of -actions to take to convert one to the other -execute all of the actions, deepest first - kinds of actions are install, update, remove and move -.fi -.RE -.P -For this \fBpackage{dep}\fP structure: \fBA{B,C}, B{C}, C{D}\fP, -this algorithm produces: -.P -.RS 2 -.nf -A -+\-\- B -+\-\- C -+\-\- D -.fi -.RE -.P -That is, the dependency from B to C is satisfied by the fact that A -already caused C to be installed at a higher level\. D is still installed -at the top level because nothing conflicts with it\. -.P -For \fBA{B,C}, B{C,D@1}, C{D@2}\fP, this algorithm produces: -.P -.RS 2 -.nf -A -+\-\- B -+\-\- C - `\-\- D@2 -+\-\- D@1 -.fi -.RE -.P -Because B's D@1 will be installed in the top level, C now has to install D@2 -privately for itself\. This algorithm is deterministic, but different trees may -be produced if two dependencies are requested for installation in a different -order\. -.P -See npm help 5 folders for a more detailed description of the specific -folder structures that npm creates\. -.SS Limitations of npm's Install Algorithm -.P -npm will refuse to install any package with an identical name to the -current package\. This can be overridden with the \fB\-\-force\fP flag, but in -most cases can simply be addressed by changing the local package name\. -.P -There are some very rare and pathological edge\-cases where a cycle can -cause npm to try to install a never\-ending tree of packages\. Here is -the simplest case: -.P -.RS 2 -.nf -A \-> B \-> A' \-> B' \-> A \-> B \-> A' \-> B' \-> A \-> \.\.\. -.fi -.RE -.P -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'\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\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\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help update -.IP \(bu 2 -npm help audit -.IP \(bu 2 -npm help link -.IP \(bu 2 -npm help rebuild -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help build -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help dist\-tag -.IP \(bu 2 -npm help uninstall -.IP \(bu 2 -npm help shrinkwrap -.IP \(bu 2 -npm help 5 package\.json - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-link.1 b/deps/node/deps/npm/man/man1/npm-link.1 deleted file mode 100644 index 292b9e50..00000000 --- a/deps/node/deps/npm/man/man1/npm-link.1 +++ /dev/null @@ -1,105 +0,0 @@ -.TH "NPM\-LINK" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-link\fR \- Symlink a package folder -.SH SYNOPSIS -.P -.RS 2 -.nf -npm link (in package dir) -npm link [<@scope>/]<pkg>[@<version>] - -alias: npm ln -.fi -.RE -.SH DESCRIPTION -.P -Package linking is a two\-step process\. -.P -First, \fBnpm link\fP in a package folder will create a symlink in the global folder -\fB{prefix}/lib/node_modules/<package>\fP that links to the package where the \fBnpm -link\fP command was executed\. (see npm help 7 \fBnpm\-config\fP for the value of \fBprefix\fP)\. It -will also link any bins in the package to \fB{prefix}/bin/{name}\fP\|\. -.P -Next, in some other location, \fBnpm link package\-name\fP will create a -symbolic link from globally\-installed \fBpackage\-name\fP to \fBnode_modules/\fP -of the current folder\. -.P -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\fP\|\. -The scope must be preceded by an @\-symbol and followed by a slash\. -.P -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 -test it iteratively without having to continually rebuild\. -.P -For example: -.P -.RS 2 -.nf -cd ~/projects/node\-redis # go into the package directory -npm link # creates global link -cd ~/projects/node\-bloggy # go into some other package directory\. -npm link redis # link\-install the package -.fi -.RE -.P -Now, any changes to ~/projects/node\-redis will be reflected in -~/projects/node\-bloggy/node_modules/node\-redis/\. Note that the link should -be to the package name, not the directory name for that package\. -.P -You may also shortcut the two steps in one\. For example, to do the -above use\-case in a shorter way: -.P -.RS 2 -.nf -cd ~/projects/node\-bloggy # go into the dir of your main project -npm link \.\./node\-redis # link the dir of your dependency -.fi -.RE -.P -The second line is the equivalent of doing: -.P -.RS 2 -.nf -(cd \.\./node\-redis; npm link) -npm link redis -.fi -.RE -.P -That is, it first creates a global link, and then links the global -installation target into your project's \fBnode_modules\fP folder\. -.P -Note that in this case, you are referring to the directory name, \fBnode\-redis\fP, -rather than the package name \fBredis\fP\|\. -.P -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 -.nf -npm link @myorg/privatepackage -.fi -.RE -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 7 developers -.IP \(bu 2 -npm help 5 package\.json -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-logout.1 b/deps/node/deps/npm/man/man1/npm-logout.1 deleted file mode 100644 index df27d4b5..00000000 --- a/deps/node/deps/npm/man/man1/npm-logout.1 +++ /dev/null @@ -1,57 +0,0 @@ -.TH "NPM\-LOGOUT" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-logout\fR \- Log out of the registry -.SH SYNOPSIS -.P -.RS 2 -.nf -npm logout [\-\-registry=<url>] [\-\-scope=<@scope>] -.fi -.RE -.SH DESCRIPTION -.P -When logged into a registry that supports token\-based authentication, tell the -server to end this token's session\. This will invalidate the token everywhere -you're using it, not just for the current environment\. -.P -When logged into a legacy registry that uses username and password authentication, this will -clear the credentials in your user configuration\. In this case, it will \fIonly\fR affect -the current environment\. -.P -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: https:// -.P -The base URL of the npm package registry\. If \fBscope\fP is also specified, -it takes precedence\. -.SS scope -.P -Default: The scope of your current project, if any, otherwise none\. -.P -If specified, you will be logged out of the specified scope\. See npm help 7 \fBnpm\-scope\fP\|\. -.P -.RS 2 -.nf -npm logout \-\-scope=@myco -.fi -.RE -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help adduser -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help whoami - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-ls.1 b/deps/node/deps/npm/man/man1/npm-ls.1 deleted file mode 100644 index 59fa5878..00000000 --- a/deps/node/deps/npm/man/man1/npm-ls.1 +++ /dev/null @@ -1,153 +0,0 @@ -.TH "NPM\-LS" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-ls\fR \- List installed packages -.SH SYNOPSIS -.P -.RS 2 -.nf -npm ls [[<@scope>/]<pkg> \.\.\.] - -aliases: list, la, ll -.fi -.RE -.SH DESCRIPTION -.P -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\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\fP in npm's source tree will show: -.P -.RS 2 -.nf -npm@6.7.0 /path/to/npm -└─┬ init\-package\-json@0\.0\.4 - └── promzard@0\.1\.5 -.fi -.RE -.P -It will print out extraneous, missing, and invalid packages\. -.P -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 -The tree shown is the logical dependency tree, based on package -dependencies, not the physical layout of your node_modules folder\. -.P -When run as \fBll\fP or \fBla\fP, it shows extended information by default\. -.SH CONFIGURATION -.SS json -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Show information in JSON format\. -.SS long -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Show extended information\. -.SS parseable -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Show parseable output instead of tree view\. -.SS global -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -List packages in the global install prefix instead of in the current -project\. -.SS depth -.RS 0 -.IP \(bu 2 -Type: Int - -.RE -.P -Max display depth of the dependency tree\. -.SS prod / production -.RS 0 -.IP \(bu 2 -Type: Boolean -.IP \(bu 2 -Default: false - -.RE -.P -Display only the dependency tree for packages in \fBdependencies\fP\|\. -.SS dev / development -.RS 0 -.IP \(bu 2 -Type: Boolean -.IP \(bu 2 -Default: false - -.RE -.P -Display only the dependency tree for packages in \fBdevDependencies\fP\|\. -.SS only -.RS 0 -.IP \(bu 2 -Type: String - -.RE -.P -When "dev" or "development", is an alias to \fBdev\fP\|\. -.P -When "prod" or "production", is an alias to \fBproduction\fP\|\. -.SS link -.RS 0 -.IP \(bu 2 -Type: Boolean -.IP \(bu 2 -Default: false - -.RE -.P -Display only dependencies which are linked -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help link -.IP \(bu 2 -npm help prune -.IP \(bu 2 -npm help outdated -.IP \(bu 2 -npm help update - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-org.1 b/deps/node/deps/npm/man/man1/npm-org.1 deleted file mode 100644 index 2cef7e05..00000000 --- a/deps/node/deps/npm/man/man1/npm-org.1 +++ /dev/null @@ -1,72 +0,0 @@ -.TH "NPM\-ORG" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-org\fR \- Manage orgs -.SH SYNOPSIS -.P -.RS 2 -.nf -npm org set <orgname> <username> [developer | admin | owner] -npm org rm <orgname> <username> -npm org ls <orgname> [<username>] -.fi -.RE -.SH EXAMPLE -.P -Add a new developer to an org: -.P -.RS 2 -.nf -$ npm org set my\-org @mx\-smith -.fi -.RE -.P -Add a new admin to an org (or change a developer to an admin): -.P -.RS 2 -.nf -$ npm org set my\-org @mx\-santos admin -.fi -.RE -.P -Remove a user from an org: -.P -.RS 2 -.nf -$ npm org rm my\-org mx\-santos -.fi -.RE -.P -List all users in an org: -.P -.RS 2 -.nf -$ npm org ls my\-org -.fi -.RE -.P -List all users in JSON format: -.P -.RS 2 -.nf -$ npm org ls my\-org \-\-json -.fi -.RE -.P -See what role a user has in an org: -.P -.RS 2 -.nf -$ npm org ls my\-org @mx\-santos -.fi -.RE -.SH DESCRIPTION -.P -You can use the \fBnpm org\fP commands to manage and view users of an organization\. -It supports adding and removing users, changing their roles, listing them, and -finding specific ones and their roles\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -Documentation on npm Orgs \fIhttps://docs\.npmjs\.com/orgs/\fR - -.RE diff --git a/deps/node/deps/npm/man/man1/npm-outdated.1 b/deps/node/deps/npm/man/man1/npm-outdated.1 deleted file mode 100644 index 7e0a18be..00000000 --- a/deps/node/deps/npm/man/man1/npm-outdated.1 +++ /dev/null @@ -1,156 +0,0 @@ -.TH "NPM\-OUTDATED" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-outdated\fR \- Check for outdated packages -.SH SYNOPSIS -.P -.RS 2 -.nf -npm outdated [[<@scope>/]<pkg> \.\.\.] -.fi -.RE -.SH DESCRIPTION -.P -This command will check the registry to see if any (or, specific) installed -packages are currently outdated\. -.P -In the output: -.RS 0 -.IP \(bu 2 -\fBwanted\fP is the maximum version of the package that satisfies the semver -range specified in \fBpackage\.json\fP\|\. If there's no available semver range (i\.e\. -you're running \fBnpm outdated \-\-global\fP, or the package isn't included in -\fBpackage\.json\fP), then \fBwanted\fP shows the currently\-installed version\. -.IP \(bu 2 -\fBlatest\fP is the version of the package tagged as latest in the registry\. -Running \fBnpm publish\fP with no special configuration will publish the package -with a dist\-tag of \fBlatest\fP\|\. This may or may not be the maximum version of -the package, or the most\-recently published version of the package, depending -on how the package's developer manages the latest npm help dist\-tag\. -.IP \(bu 2 -\fBlocation\fP is where in the dependency tree the package is located\. Note that -\fBnpm outdated\fP defaults to a depth of 0, so unless you override that, you'll -always be seeing only top\-level dependencies that are outdated\. -.IP \(bu 2 -\fBpackage type\fP (when using \fB\-\-long\fP / \fB\-l\fP) tells you whether this package is -a \fBdependency\fP or a \fBdevDependency\fP\|\. Packages not included in \fBpackage\.json\fP -are always marked \fBdependencies\fP\|\. -.IP \(bu 2 -\fBhomepage\fP (when using \fB\-\-long\fP / \fB\-l\fP) is the \fBhomepage\fP value contained in the package's \fBpackage\.json\fP -.IP \(bu 2 -Red means there's a newer version matching your semver requirements, so you should update now\. -.IP \(bu 2 -Yellow indicates that there's a newer version above your semver requirements (usually new major, or new 0\.x minor) so proceed with caution\. - -.RE -.SS An example -.P -.RS 2 -.nf -$ npm outdated -Package Current Wanted Latest Location -glob 5\.0\.15 5\.0\.15 6\.0\.1 test\-outdated\-output -nothingness 0\.0\.3 git git test\-outdated\-output -npm 3\.5\.1 3\.5\.2 3\.5\.1 test\-outdated\-output -local\-dev 0\.0\.3 linked linked test\-outdated\-output -once 1\.3\.2 1\.3\.3 1\.3\.3 test\-outdated\-output -.fi -.RE -.P -With these \fBdependencies\fP: -.P -.RS 2 -.nf -{ - "glob": "^5\.0\.15", - "nothingness": "github:othiym23/nothingness#master", - "npm": "^3\.5\.1", - "once": "^1\.3\.1" -} -.fi -.RE -.P -A few things to note: -.RS 0 -.IP \(bu 2 -\fBglob\fP requires \fB^5\fP, which prevents npm from installing \fBglob@6\fP, which is -outside the semver range\. -.IP \(bu 2 -Git dependencies will always be reinstalled, because of how they're specified\. -The installed committish might satisfy the dependency specifier (if it's -something immutable, like a commit SHA), or it might not, so \fBnpm outdated\fP and -\fBnpm update\fP have to fetch Git repos to check\. This is why currently doing a -reinstall of a Git dependency always forces a new clone and install\. -.IP \(bu 2 -\fBis marked as "wanted", but "latest" is\fP\fBbecause npm -uses dist\-tags to manage its\fPlatest\fBand\fPnext\fBrelease channels\.\fPnpm update\fBwill install the _newest_ version, but\fPnpm install npm\fB(with no semver range) -will install whatever's tagged as\fPlatest`\. -.IP \(bu 2 -\fBonce\fP is just plain out of date\. Reinstalling \fBnode_modules\fP from scratch or -running \fBnpm update\fP will bring it up to spec\. - -.RE -.SH CONFIGURATION -.SS json -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Show information in JSON format\. -.SS long -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Show extended information\. -.SS parseable -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Show parseable output instead of tree view\. -.SS global -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Check packages in the global install prefix instead of in the current -project\. -.SS depth -.RS 0 -.IP \(bu 2 -Default: 0 -.IP \(bu 2 -Type: Int - -.RE -.P -Max depth for checking dependency tree\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help update -.IP \(bu 2 -npm help dist\-tag -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help 5 folders - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-owner.1 b/deps/node/deps/npm/man/man1/npm-owner.1 deleted file mode 100644 index c7209ddc..00000000 --- a/deps/node/deps/npm/man/man1/npm-owner.1 +++ /dev/null @@ -1,53 +0,0 @@ -.TH "NPM\-OWNER" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-owner\fR \- Manage package owners -.SH SYNOPSIS -.P -.RS 2 -.nf -npm owner add <user> [<@scope>/]<pkg> -npm owner rm <user> [<@scope>/]<pkg> -npm owner ls [<@scope>/]<pkg> - -aliases: author -.fi -.RE -.SH DESCRIPTION -.P -Manage ownership of published packages\. -.RS 0 -.IP \(bu 2 -ls: -List all the users who have access to modify a package and push new versions\. -Handy when you need to know who to bug for help\. -.IP \(bu 2 -add: -Add a new user as a maintainer of a package\. This user is enabled to modify -metadata, publish new versions, and add other owners\. -.IP \(bu 2 -rm: -Remove a user from the package owner list\. This immediately revokes their -privileges\. - -.RE -.P -Note that there is only one level of access\. Either you can modify a package, -or you can't\. Future versions may contain more fine\-grained access levels, but -that is not implemented at this time\. -.P -If you have two\-factor authentication enabled with \fBauth\-and\-writes\fP then -you'll need to include an otp on the command line when changing ownership -with \fB\-\-otp\fP\|\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help adduser -.IP \(bu 2 -npm help 7 disputes - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-pack.1 b/deps/node/deps/npm/man/man1/npm-pack.1 deleted file mode 100644 index 34af6856..00000000 --- a/deps/node/deps/npm/man/man1/npm-pack.1 +++ /dev/null @@ -1,40 +0,0 @@ -.TH "NPM\-PACK" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-pack\fR \- Create a tarball from a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm pack [[<@scope>/]<pkg>\.\.\.] [\-\-dry\-run] -.fi -.RE -.SH DESCRIPTION -.P -For anything that's installable (that is, a package folder, tarball, -tarball url, name@tag, name@version, name, or scoped name), this -command will fetch it to the cache, and then copy the tarball to the -current working 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 -overwritten the second time\. -.P -If no arguments are supplied, then npm packs the current package folder\. -.P -The \fB\-\-dry\-run\fP argument will do everything that pack usually does without -actually packing anything\. Reports on what would have gone into the tarball\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help cache -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-ping.1 b/deps/node/deps/npm/man/man1/npm-ping.1 deleted file mode 100644 index 200f5138..00000000 --- a/deps/node/deps/npm/man/man1/npm-ping.1 +++ /dev/null @@ -1,39 +0,0 @@ -.TH "NPM\-PING" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-ping\fR \- Ping npm registry -.SH SYNOPSIS -.P -.RS 2 -.nf -npm ping [\-\-registry <registry>] -.fi -.RE -.SH DESCRIPTION -.P -Ping the configured or given npm registry and verify authentication\. -If it works it will output something like: -.P -.RS 2 -.nf -Ping success: {*Details about registry*} -.fi -.RE -.P -otherwise you will get: -.P -.RS 2 -.nf -Ping error: {*Detail about error} -.fi -.RE -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-prefix.1 b/deps/node/deps/npm/man/man1/npm-prefix.1 deleted file mode 100644 index 372647ec..00000000 --- a/deps/node/deps/npm/man/man1/npm-prefix.1 +++ /dev/null @@ -1,35 +0,0 @@ -.TH "NPM\-PREFIX" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-prefix\fR \- Display prefix -.SH SYNOPSIS -.P -.RS 2 -.nf -npm prefix [\-g] -.fi -.RE -.SH DESCRIPTION -.P -Print the local prefix to standard out\. This is the closest parent directory -to contain a \fBpackage\.json\fP file or \fBnode_modules\fP directory, unless \fB\-g\fP is -also specified\. -.P -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 -npm help root -.IP \(bu 2 -npm help bin -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-profile.1 b/deps/node/deps/npm/man/man1/npm-profile.1 deleted file mode 100644 index 1bd7dcc2..00000000 --- a/deps/node/deps/npm/man/man1/npm-profile.1 +++ /dev/null @@ -1,91 +0,0 @@ -.TH "NPM\-PROFILE" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-profile\fR \- Change settings on your registry profile -.SH SYNOPSIS -.P -.RS 2 -.nf -npm profile get [\-\-json|\-\-parseable] [<property>] -npm profile set [\-\-json|\-\-parseable] <property> <value> -npm profile set password -npm profile enable\-2fa [auth\-and\-writes|auth\-only] -npm profile disable\-2fa -.fi -.RE -.SH DESCRIPTION -.P -Change your profile information on the registry\. This not be available if -you're using a non\-npmjs registry\. -.RS 0 -.IP \(bu 2 -\fBnpm profile get [<property>]\fP: -Display all of the properties of your profile, or one or more specific -properties\. It looks like: - -.RE -.P -.RS 2 -.nf -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| name | example | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| email | me@example\.com (verified) | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| two factor auth | auth\-and\-writes | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| fullname | Example User | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| homepage | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| freenode | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| twitter | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| github | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| created | 2015\-02\-26T01:38:35\.892Z | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| updated | 2017\-10\-02T21:29:45\.922Z | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -.fi -.RE -.RS 0 -.IP \(bu 2 -\fBnpm profile set <property> <value>\fP: -Set the value of a profile property\. You can set the following properties this way: - email, fullname, homepage, freenode, twitter, github -.IP \(bu 2 -\fBnpm profile set password\fP: -Change your password\. This is interactive, you'll be prompted for your -current password and a new password\. You'll also be prompted for an OTP -if you have two\-factor authentication enabled\. -.IP \(bu 2 -\fBnpm profile enable\-2fa [auth\-and\-writes|auth\-only]\fP: -Enables two\-factor authentication\. Defaults to \fBauth\-and\-writes\fP mode\. Modes are: -.RS 0 -.IP \(bu 2 -\fBauth\-only\fP: Require an OTP when logging in or making changes to your -account's authentication\. The OTP will be required on both the website -and the command line\. -.IP \(bu 2 -\fBauth\-and\-writes\fP: Requires an OTP at all the times \fBauth\-only\fP does, and also requires one when -publishing a module, setting the \fBlatest\fP dist\-tag, or changing access -via \fBnpm access\fP and \fBnpm owner\fP\|\. - -.RE -.IP \(bu 2 -\fBnpm profile disable\-2fa\fP: -Disables two\-factor authentication\. - -.RE -.SH DETAILS -.P -All of the \fBnpm profile\fP subcommands accept \fB\-\-json\fP and \fB\-\-parseable\fP and -will tailor their output based on those\. Some of these commands may not be -available on non npmjs\.com registries\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 7 config - -.RE diff --git a/deps/node/deps/npm/man/man1/npm-prune.1 b/deps/node/deps/npm/man/man1/npm-prune.1 deleted file mode 100644 index 6a3ed6d6..00000000 --- a/deps/node/deps/npm/man/man1/npm-prune.1 +++ /dev/null @@ -1,46 +0,0 @@ -.TH "NPM\-PRUNE" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-prune\fR \- Remove extraneous packages -.SH SYNOPSIS -.P -.RS 2 -.nf -npm prune [[<@scope>/]<pkg>\.\.\.] [\-\-production] [\-\-dry\-run] [\-\-json] -.fi -.RE -.SH DESCRIPTION -.P -This command removes "extraneous" packages\. If a package name is -provided, then only packages matching one of the supplied names are -removed\. -.P -Extraneous packages are packages that are not listed on the parent -package's dependencies list\. -.P -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\-\-no\-production\fP will -negate \fBNODE_ENV\fP being set to \fBproduction\fP\|\. -.P -If the \fB\-\-dry\-run\fP flag is used then no changes will actually be made\. -.P -If the \fB\-\-json\fP flag is used then the changes \fBnpm prune\fP made (or would -have made with \fB\-\-dry\-run\fP) are printed as a JSON object\. -.P -In normal operation with package\-locks enabled, extraneous modules are -pruned automatically when modules are installed and you'll only need -this command with the \fB\-\-production\fP flag\. -.P -If you've disabled package\-locks then extraneous modules will not be removed -and it's up to you to run \fBnpm prune\fP from time\-to\-time to remove them\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help uninstall -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help ls - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-publish.1 b/deps/node/deps/npm/man/man1/npm-publish.1 deleted file mode 100644 index 934a9ad8..00000000 --- a/deps/node/deps/npm/man/man1/npm-publish.1 +++ /dev/null @@ -1,91 +0,0 @@ -.TH "NPM\-PUBLISH" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-publish\fR \- Publish a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm publish [<tarball>|<folder>] [\-\-tag <tag>] [\-\-access <public|restricted>] [\-\-otp otpcode] [\-\-dry\-run] - -Publishes '\.' if no argument supplied -Sets tag 'latest' if no \-\-tag specified -.fi -.RE -.SH DESCRIPTION -.P -Publishes a package to the registry so that it can be installed by name\. All -files in the package directory are included if no local \fB\|\.gitignore\fP or -\fB\|\.npmignore\fP file exists\. If both files exist and a file is ignored by -\fB\|\.gitignore\fP but not by \fB\|\.npmignore\fP then it will be included\. See -npm help 7 \fBnpm\-developers\fP for full 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\fP in the name -(see npm help 5 \fBpackage\.json\fP)\. -.RS 0 -.IP \(bu 2 -\fB<folder>\fP: -A folder containing a package\.json file -.IP \(bu 2 -\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>]\fP -Registers the published package with the given tag, such that \fBnpm install -<name>@<tag>\fP will install this version\. By default, \fBnpm publish\fP updates -and \fBnpm install\fP installs the \fBlatest\fP tag\. See npm help \fBnpm\-dist\-tag\fP for -details about tags\. -.IP \(bu 2 -\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\fP\|\. -If you don't have a paid account, you must publish with \fB\-\-access public\fP -to publish scoped packages\. -.IP \(bu 2 -\fB[\-\-otp <otpcode>]\fP -If you have two\-factor authentication enabled in \fBauth\-and\-writes\fP mode -then you can provide a code from your authenticator with this\. If you -don't include this and you're running from a TTY then you'll be prompted\. -.IP \(bu 2 -\fB[\-\-dry\-run]\fP -As of \fBnpm@6\fP, does everything publish would do except actually publishing -to the registry\. Reports the details of what would have been published\. - -.RE -.P -Fails if the package name and version combination already exists in -the specified registry\. -.P -Once a package is published with a given name and version, that -specific name and version combination can never be used again, even if -it is removed with npm help unpublish\. -.P -As of \fBnpm@5\fP, both a sha1sum and an integrity field with a sha512sum of the -tarball will be submitted to the registry during publication\. Subsequent -installs will use the strongest supported algorithm to verify downloads\. -.P -Similar to \fB\-\-dry\-run\fP see npm help \fBnpm\-pack\fP, which figures out the files to be -included and packs them into a tarball to be uploaded to the registry\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help 7 scope -.IP \(bu 2 -npm help adduser -.IP \(bu 2 -npm help owner -.IP \(bu 2 -npm help deprecate -.IP \(bu 2 -npm help dist\-tag -.IP \(bu 2 -npm help pack -.IP \(bu 2 -npm help profile - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-rebuild.1 b/deps/node/deps/npm/man/man1/npm-rebuild.1 deleted file mode 100644 index 8005c951..00000000 --- a/deps/node/deps/npm/man/man1/npm-rebuild.1 +++ /dev/null @@ -1,26 +0,0 @@ -.TH "NPM\-REBUILD" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-rebuild\fR \- Rebuild a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm rebuild [[<@scope>/<name>]\.\.\.] - -alias: npm rb -.fi -.RE -.SH DESCRIPTION -.P -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 -.RS 0 -.IP \(bu 2 -npm help build -.IP \(bu 2 -npm help install - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-repo.1 b/deps/node/deps/npm/man/man1/npm-repo.1 deleted file mode 100644 index 261d44a8..00000000 --- a/deps/node/deps/npm/man/man1/npm-repo.1 +++ /dev/null @@ -1,36 +0,0 @@ -.TH "NPM\-REPO" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-repo\fR \- Open package repository page in the browser -.SH SYNOPSIS -.P -.RS 2 -.nf -npm repo [<pkg>] -.fi -.RE -.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\fP -config param\. If no 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"\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\fP command to open websites\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help docs -.IP \(bu 2 -npm help config - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-restart.1 b/deps/node/deps/npm/man/man1/npm-restart.1 deleted file mode 100644 index 084f5690..00000000 --- a/deps/node/deps/npm/man/man1/npm-restart.1 +++ /dev/null @@ -1,61 +0,0 @@ -.TH "NPM\-RESTART" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-restart\fR \- Restart a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm restart [\-\- <args>] -.fi -.RE -.SH DESCRIPTION -.P -This restarts a package\. -.P -This runs a package's "stop", "restart", and "start" scripts, and associated -pre\- and post\- scripts, in the order given below: -.RS 0 -.IP 1. 3 -prerestart -.IP 2. 3 -prestop -.IP 3. 3 -stop -.IP 4. 3 -poststop -.IP 5. 3 -restart -.IP 6. 3 -prestart -.IP 7. 3 -start -.IP 8. 3 -poststart -.IP 9. 3 -postrestart - -.RE -.SH NOTE -.P -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\fP major version 2\. A change in this -behavior will be accompanied by an increase in major version number -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help run\-script -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help test -.IP \(bu 2 -npm help start -.IP \(bu 2 -npm help stop -.IP \(bu 2 -npm apihelp restart - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-root.1 b/deps/node/deps/npm/man/man1/npm-root.1 deleted file mode 100644 index fd4246d8..00000000 --- a/deps/node/deps/npm/man/man1/npm-root.1 +++ /dev/null @@ -1,30 +0,0 @@ -.TH "NPM\-ROOT" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-root\fR \- Display npm root -.SH SYNOPSIS -.P -.RS 2 -.nf -npm root [\-g] -.fi -.RE -.SH DESCRIPTION -.P -Print the effective \fBnode_modules\fP folder to standard out\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help prefix -.IP \(bu 2 -npm help bin -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-run-script.1 b/deps/node/deps/npm/man/man1/npm-run-script.1 deleted file mode 100644 index e349dab4..00000000 --- a/deps/node/deps/npm/man/man1/npm-run-script.1 +++ /dev/null @@ -1,105 +0,0 @@ -.TH "NPM\-RUN\-SCRIPT" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-run-script\fR \- Run arbitrary package scripts -.SH SYNOPSIS -.P -.RS 2 -.nf -npm run\-script <command> [\-\-silent] [\-\- <args>\.\.\.] - -alias: npm run -.fi -.RE -.SH DESCRIPTION -.P -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 ` \fIhttps://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 \fIhttps://goo\.gl/KxMmtG\fR to delimit the end of the options\. npm will pass -all the arguments after the \fB\-\-\fP directly to your script: -.P -.RS 2 -.nf -npm run test \-\- \-\-grep="pattern" -.fi -.RE -.P -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\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\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 -.nf -"scripts": {"test": "tap test/\\*\.js"} -.fi -.RE -.P -instead of -.P -.RS 2 -.nf -"scripts": {"test": "node_modules/\.bin/tap test/\\*\.js"} -.fi -.RE -.P -to run your tests\. -.P -The actual shell your script is run within is platform dependent\. By default, -on Unix\-like systems it is the \fB/bin/sh\fP command, on Windows it is the \fBcmd\.exe\fP\|\. -The actual shell referred to by \fB/bin/sh\fP also depends on the system\. -As of ` \fIhttps://github\.com/npm/npm/releases/tag/v5\.1\.0\fR you can -customize the shell with the \fBscript\-shell\fP configuration\. -.P -Scripts are run from the root of the module, regardless of what your current -working directory is when you call \fBnpm run\fP\|\. If you want your script to -use different behavior based on what subdirectory you're in, you can use the -\fBINIT_CWD\fP environment variable, which holds the full path you were in when -you ran \fBnpm run\fP\|\. -.P -\fBnpm run\fP sets the \fBNODE\fP environment variable to the \fBnode\fP executable with -which \fBnpm\fP is executed\. Also, if the \fB\-\-scripts\-prepend\-node\-path\fP is passed, -the directory within which \fBnode\fP resides is added to the -\fBPATH\fP\|\. If \fB\-\-scripts\-prepend\-node\-path=auto\fP is passed (which has been the -default in \fBnpm\fP v3), this is only performed when that \fBnode\fP executable is -not found in the \fBPATH\fP\|\. -.P -If you try to run a script without having a \fBnode_modules\fP directory and it fails, -you will be given a warning to run \fBnpm install\fP, just in case you've forgotten\. -.P -You can use the \fB\-\-silent\fP flag to prevent showing \fBnpm ERR!\fP output on error\. -.P -You can use the \fB\-\-if\-present\fP flag to avoid exiting with a non\-zero exit code -when the script is undefined\. This lets you run potentially undefined scripts -without breaking the execution chain\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help test -.IP \(bu 2 -npm help start -.IP \(bu 2 -npm help restart -.IP \(bu 2 -npm help stop -.IP \(bu 2 -npm help 7 config - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-search.1 b/deps/node/deps/npm/man/man1/npm-search.1 deleted file mode 100644 index 95a8d096..00000000 --- a/deps/node/deps/npm/man/man1/npm-search.1 +++ /dev/null @@ -1,138 +0,0 @@ -.TH "NPM\-SEARCH" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-search\fR \- Search for packages -.SH SYNOPSIS -.P -.RS 2 -.nf -npm search [\-l|\-\-long] [\-\-json] [\-\-parseable] [\-\-no\-description] [search terms \.\.\.] - -aliases: s, se, find -.fi -.RE -.SH DESCRIPTION -.P -Search the registry for packages matching the search terms\. \fBnpm search\fP -performs a linear, incremental, lexically\-ordered search through package -metadata for all files in the registry\. If color is enabled, it will further -highlight the matches in the results\. -.P -Additionally, using the \fB\-\-searchopts\fP and \fB\-\-searchexclude\fP options paired with -more search terms will respectively include and exclude further patterns\. The -main difference between \fB\-\-searchopts\fP and the standard search terms is that the -former does not highlight results in the output and can be used for more -fine\-grained filtering\. Additionally, both of these can be added to \fB\|\.npmrc\fP for -default search filtering behavior\. -.P -Search also allows targeting of maintainers in search results, by prefixing -their npm username with \fB=\fP\|\. -.P -If a term starts with \fB/\fP, then it's interpreted as a regular expression and -supports standard JavaScript RegExp syntax\. A trailing \fB/\fP will be ignored in -this case\. (Note that many regular expression characters must be escaped or -quoted in most shells\.) -.SS A Note on caching -.SH CONFIGURATION -.SS description -.RS 0 -.IP \(bu 2 -Default: true -.IP \(bu 2 -Type: Boolean - -.RE -.P -Used as \fB\-\-no\-description\fP, disables search matching in package descriptions and -suppresses display of that field in results\. -.SS json -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Output search results as a JSON array\. -.SS parseable -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Output search results as lines with tab\-separated columns\. -.SS long -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Display full package descriptions and other long text across multiple -lines\. When disabled (default) search results are truncated to fit -neatly on a single line\. Modules with extremely long names will -fall on multiple lines\. -.SS searchopts -.RS 0 -.IP \(bu 2 -Default: "" -.IP \(bu 2 -Type: String - -.RE -.P -Space\-separated options that are always passed to search\. -.SS searchexclude -.RS 0 -.IP \(bu 2 -Default: "" -.IP \(bu 2 -Type: String - -.RE -.P -Space\-separated options that limit the results from search\. -.SS searchstaleness -.RS 0 -.IP \(bu 2 -Default: 900 (15 minutes) -.IP \(bu 2 -Type: Number - -.RE -.P -The age of the cache, in seconds, before another registry request is made\. -.SS registry -.RS 0 -.IP \(bu 2 -Default: https:// -.IP \(bu 2 -Type: url - -.RE -.P -Search the specified registry for modules\. If you have configured npm to point -to a different default registry, such as your internal private module -repository, \fBnpm search\fP will default to that registry when searching\. Pass a -different registry url such as the default above in order to override this -setting\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help view - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-shrinkwrap.1 b/deps/node/deps/npm/man/man1/npm-shrinkwrap.1 deleted file mode 100644 index 3f9658fe..00000000 --- a/deps/node/deps/npm/man/man1/npm-shrinkwrap.1 +++ /dev/null @@ -1,38 +0,0 @@ -.TH "NPM\-SHRINKWRAP" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-shrinkwrap\fR \- Lock down dependency versions for publication -.SH SYNOPSIS -.P -.RS 2 -.nf -npm shrinkwrap -.fi -.RE -.SH DESCRIPTION -.P -This command repurposes \fBpackage\-lock\.json\fP into a publishable -\fBnpm\-shrinkwrap\.json\fP or simply creates a new one\. The file created and updated -by this command will then take precedence over any other existing or future -\fBpackage\-lock\.json\fP files\. For a detailed explanation of the design and purpose -of package locks in npm, see npm help 5 package\-locks\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help run\-script -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help 5 package\.json -.IP \(bu 2 -npm help 5 package\-locks -.IP \(bu 2 -npm help 5 package\-lock\.json -.IP \(bu 2 -npm help 5 shrinkwrap\.json -.IP \(bu 2 -npm help ls - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-star.1 b/deps/node/deps/npm/man/man1/npm-star.1 deleted file mode 100644 index ae8c6166..00000000 --- a/deps/node/deps/npm/man/man1/npm-star.1 +++ /dev/null @@ -1,30 +0,0 @@ -.TH "NPM\-STAR" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-star\fR \- Mark your favorite packages -.SH SYNOPSIS -.P -.RS 2 -.nf -npm star [<pkg>\.\.\.] -npm unstar [<pkg>\.\.\.] -.fi -.RE -.SH DESCRIPTION -.P -"Starring" a package means that you have some interest in it\. It's -a vaguely positive way to show that you care\. -.P -"Unstarring" is the same thing, but in reverse\. -.P -It's a boolean thing\. Starring repeatedly has no additional effect\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help view -.IP \(bu 2 -npm help whoami -.IP \(bu 2 -npm help adduser - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-stars.1 b/deps/node/deps/npm/man/man1/npm-stars.1 deleted file mode 100644 index 2f6038cb..00000000 --- a/deps/node/deps/npm/man/man1/npm-stars.1 +++ /dev/null @@ -1,30 +0,0 @@ -.TH "NPM\-STARS" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-stars\fR \- View packages marked as favorites -.SH SYNOPSIS -.P -.RS 2 -.nf -npm stars [<user>] -.fi -.RE -.SH DESCRIPTION -.P -If you have starred a lot of neat things and want to find them again -quickly this command lets you do just that\. -.P -You may also want to see your friend's favorite packages, in this case -you will most certainly enjoy this command\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help star -.IP \(bu 2 -npm help view -.IP \(bu 2 -npm help whoami -.IP \(bu 2 -npm help adduser - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-start.1 b/deps/node/deps/npm/man/man1/npm-start.1 deleted file mode 100644 index 7ea6362b..00000000 --- a/deps/node/deps/npm/man/man1/npm-start.1 +++ /dev/null @@ -1,34 +0,0 @@ -.TH "NPM\-START" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-start\fR \- Start a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm start [\-\- <args>] -.fi -.RE -.SH DESCRIPTION -.P -This runs an arbitrary command specified in the package's \fB"start"\fP property of -its \fB"scripts"\fP object\. If no \fB"start"\fP property is specified on the -\fB"scripts"\fP object, it will run \fBnode server\.js\fP\|\. -.P -As of ` \fIhttps://blog\.npmjs\.org/post/98131109725/npm\-2\-0\-0\fR, you can -use custom arguments when executing scripts\. Refer to npm help run\-script for -more details\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help run\-script -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help test -.IP \(bu 2 -npm help restart -.IP \(bu 2 -npm help stop - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-stop.1 b/deps/node/deps/npm/man/man1/npm-stop.1 deleted file mode 100644 index 2fa4d88a..00000000 --- a/deps/node/deps/npm/man/man1/npm-stop.1 +++ /dev/null @@ -1,28 +0,0 @@ -.TH "NPM\-STOP" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-stop\fR \- Stop a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm stop [\-\- <args>] -.fi -.RE -.SH DESCRIPTION -.P -This runs a package's "stop" script, if one was provided\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help run\-script -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help test -.IP \(bu 2 -npm help start -.IP \(bu 2 -npm help restart - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-team.1 b/deps/node/deps/npm/man/man1/npm-team.1 deleted file mode 100644 index 6ed65ab4..00000000 --- a/deps/node/deps/npm/man/man1/npm-team.1 +++ /dev/null @@ -1,67 +0,0 @@ -.TH "NPM\-TEAM" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-team\fR \- Manage organization teams and team memberships -.SH SYNOPSIS -.P -.RS 2 -.nf -npm team create <scope:team> -npm team destroy <scope:team> - -npm team add <scope:team> <user> -npm team rm <scope:team> <user> - -npm team ls <scope>|<scope:team> - -npm team edit <scope:team> -.fi -.RE -.SH DESCRIPTION -.P -Used to manage teams in organizations, and change team memberships\. Does not -handle permissions for packages\. -.P -Teams must always be fully qualified with the organization/scope they belong to -when operating on them, separated by a colon (\fB:\fP)\. That is, if you have a -\fBdevelopers\fP team on a \fBfoo\fP organization, you must always refer to that team as -\fBfoo:developers\fP in these commands\. -.RS 0 -.IP \(bu 2 -create / destroy: -Create a new team, or destroy an existing one\. -.IP \(bu 2 -add / rm: -Add a user to an existing team, or remove a user from a team they belong to\. -.IP \(bu 2 -ls: -If performed on an organization name, will return a list of existing teams -under that organization\. If performed on a team, it will instead return a list -of all users belonging to that particular team\. -.IP \(bu 2 -edit: -Edit a current team\. - -.RE -.SH DETAILS -.P -\fBnpm team\fP always operates directly on the current registry, configurable from -the command line using \fB\-\-registry=<registry url>\fP\|\. -.P -In order to create teams and manage team membership, you must be a \fIteam admin\fR -under the given organization\. Listing teams and team memberships may be done by -any member of the organizations\. -.P -Organization creation and management of team admins and \fIorganization\fR members -is done through the website, not the npm CLI\. -.P -To use teams to manage permissions on packages belonging to your organization, -use the \fBnpm access\fP command to grant or revoke the appropriate permissions\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help access -.IP \(bu 2 -npm help 7 registry - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-test.1 b/deps/node/deps/npm/man/man1/npm-test.1 deleted file mode 100644 index 0183a8e0..00000000 --- a/deps/node/deps/npm/man/man1/npm-test.1 +++ /dev/null @@ -1,30 +0,0 @@ -.TH "NPM\-TEST" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-test\fR \- Test a package -.SH SYNOPSIS -.P -.RS 2 -.nf - npm test [\-\- <args>] - - aliases: t, tst -.fi -.RE -.SH DESCRIPTION -.P -This runs a package's "test" script, if one was provided\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help run\-script -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help start -.IP \(bu 2 -npm help restart -.IP \(bu 2 -npm help stop - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-token.1 b/deps/node/deps/npm/man/man1/npm-token.1 deleted file mode 100644 index d7ab2e18..00000000 --- a/deps/node/deps/npm/man/man1/npm-token.1 +++ /dev/null @@ -1,73 +0,0 @@ -.TH "NPM\-TOKEN" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-token\fR \- Manage your authentication tokens -.SH SYNOPSIS -.P -.RS 2 -.nf -npm token list [\-\-json|\-\-parseable] -npm token create [\-\-read\-only] [\-\-cidr=1\.1\.1\.1/24,2\.2\.2\.2/16] -npm token revoke <id|token> -.fi -.RE -.SH DESCRIPTION -.P -This lets you list, create and revoke authentication tokens\. -.RS 0 -.IP \(bu 2 -\fBnpm token list\fP: -Shows a table of all active authentication tokens\. You can request this as -JSON with \fB\-\-json\fP or tab\-separated values with \fB\-\-parseable\fP\|\. -.P -.RS 2 -.nf -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| id | token | created | read\-only | CIDR whitelist | -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 7f3134 | 1fa9ba… | 2017\-10\-02 | yes | | -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| c03241 | af7aef… | 2017\-10\-02 | no | 192\.168\.0\.1/24 | -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| e0cf92 | 3a436a… | 2017\-10\-02 | no | | -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 63eb9d | 74ef35… | 2017\-09\-28 | no | | -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 2daaa8 | cbad5f… | 2017\-09\-26 | no | | -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 68c2fe | 127e51… | 2017\-09\-23 | no | | -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| 6334e1 | 1dadd1… | 2017\-09\-23 | no | | -+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -.fi -.RE -.IP \(bu 2 -\fBnpm token create [\-\-read\-only] [\-\-cidr=<cidr\-ranges>]\fP: -Create a new authentication token\. It can be \fB\-\-read\-only\fP or accept a list of -CIDR \fIhttps://en\.wikipedia\.org/wiki/Classless_Inter\-Domain_Routing\fR ranges to -limit use of this token to\. This will prompt you for your password, and, if you have -two\-factor authentication enabled, an otp\. - -.RE -.P -.RS 2 -.nf -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| token | a73c9572\-f1b9\-8983\-983d\-ba3ac3cc913d | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| cidr_whitelist | | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| readonly | false | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -| created | 2017\-10\-02T07:52:24\.838Z | -+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+ -.fi -.RE -.RS 0 -.IP \(bu 2 -\fBnpm token revoke <token|id>\fP: -This removes an authentication token, making it immediately unusable\. This can accept -both complete tokens (as you get back from \fBnpm token create\fP and will -find in your \fB\|\.npmrc\fP) and ids as seen in the \fBnpm token list\fP output\. -This will NOT accept the truncated token found in \fBnpm token list\fP output\. - -.RE diff --git a/deps/node/deps/npm/man/man1/npm-uninstall.1 b/deps/node/deps/npm/man/man1/npm-uninstall.1 deleted file mode 100644 index 07c413e2..00000000 --- a/deps/node/deps/npm/man/man1/npm-uninstall.1 +++ /dev/null @@ -1,75 +0,0 @@ -.TH "NPM\-UNINSTALL" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-uninstall\fR \- Remove a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm uninstall [<@scope>/]<pkg>[@<version>]\.\.\. [\-S|\-\-save|\-D|\-\-save\-dev|\-O|\-\-save\-optional|\-\-no\-save] - -aliases: remove, rm, r, un, unlink -.fi -.RE -.SH DESCRIPTION -.P -This uninstalls a package, completely removing everything npm installed -on its behalf\. -.P -Example: -.P -.RS 2 -.nf -npm uninstall sax -.fi -.RE -.P -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\fP takes 3 exclusive, optional flags which save or update -the package version in your main package\.json: -.RS 0 -.IP \(bu 2 -\fB\-S, \-\-save\fP: Package will be removed from your \fBdependencies\fP\|\. -.IP \(bu 2 -\fB\-D, \-\-save\-dev\fP: Package will be removed from your \fBdevDependencies\fP\|\. -.IP \(bu 2 -\fB\-O, \-\-save\-optional\fP: Package will be removed from your \fBoptionalDependencies\fP\|\. -.IP \(bu 2 -\fB\-\-no\-save\fP: Package will not be removed from your \fBpackage\.json\fP file\. - -.RE -.P -Further, if you have an \fBnpm\-shrinkwrap\.json\fP then it will be updated as -well\. -.P -Scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\. -.P -Examples: -.P -.RS 2 -.nf -npm uninstall sax \-\-save -npm uninstall @myorg/privatepackage \-\-save -npm uninstall node\-tap \-\-save\-dev -npm uninstall dtrace\-provider \-\-save\-optional -npm uninstall lodash \-\-no\-save -.fi -.RE -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help prune -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-unpublish.1 b/deps/node/deps/npm/man/man1/npm-unpublish.1 deleted file mode 100644 index 25eb7044..00000000 --- a/deps/node/deps/npm/man/man1/npm-unpublish.1 +++ /dev/null @@ -1,54 +0,0 @@ -.TH "NPM\-UNPUBLISH" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-unpublish\fR \- Remove a package from the registry -.SH SYNOPSIS -.P -.RS 2 -.nf -npm unpublish [<@scope>/]<pkg>[@<version>] -.fi -.RE -.SH WARNING -.P -\fBIt is generally considered bad behavior to remove versions of a library -that others are depending on!\fR -.P -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\. -.SH DESCRIPTION -.P -This removes a package version from the registry, deleting its -entry and removing the tarball\. -.P -If no version is specified, or if all versions are removed then -the root package entry is removed from the registry entirely\. -.P -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\. Additionally, -new versions of packages with every version unpublished may not -be republished until 24 hours have passed\. -.P -With the default registry (\fBregistry\.npmjs\.org\fP), unpublish is -only allowed with versions published in the last 72 hours\. If you -are trying to unpublish a version published longer ago than that, -contact \|\. -.P -The scope is optional and follows the usual rules for npm help 7 \fBnpm\-scope\fP\|\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help deprecate -.IP \(bu 2 -npm help publish -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help adduser -.IP \(bu 2 -npm help owner - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-update.1 b/deps/node/deps/npm/man/man1/npm-update.1 deleted file mode 100644 index 6486b8ae..00000000 --- a/deps/node/deps/npm/man/man1/npm-update.1 +++ /dev/null @@ -1,141 +0,0 @@ -.TH "NPM\-UPDATE" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-update\fR \- Update a package -.SH SYNOPSIS -.P -.RS 2 -.nf -npm update [\-g] [<pkg>\.\.\.] - -aliases: up, upgrade -.fi -.RE -.SH DESCRIPTION -.P -This command will update all the packages listed to the latest version -(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\fP flag will cause \fBdevDependencies\fP to be processed -as well\. -.P -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 \fB, the\fPnpm update\fBwill only inspect top\-level packages\. -Prior versions of\fPnpm\fBwould also recursively inspect all dependencies\. -To get the old behavior, use\fPnpm \-\-depth 9999 update`\. -.P -As of \fB, the\fPnpm update\fBwill change\fPpackage\.json\fBto save the -new version as the minimum required dependency\. To get the old behavior, -use\fPnpm update \-\-no\-save`\. -.SH EXAMPLES -.P -IMPORTANT VERSION NOTE: these examples assume \fBor later\. For -older versions of\fPnpm\fB, you must specify\fP\-\-depth 0` to get the behavior -described below\. -.P -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 -{ - "dist\-tags": { "latest": "1\.2\.2" }, - "versions": [ - "1\.2\.2", - "1\.2\.1", - "1\.2\.0", - "1\.1\.2", - "1\.1\.1", - "1\.0\.0", - "0\.4\.1", - "0\.4\.0", - "0\.2\.0" - ] -} -.fi -.RE -.SS Caret Dependencies -.P -If \fBapp\fP\|'s \fBpackage\.json\fP contains: -.P -.RS 2 -.nf -"dependencies": { - "dep1": "^1\.1\.1" -} -.fi -.RE -.P -Then \fBnpm update\fP will install \fB, because\fP1\.2\.2\fBis\fPlatest\fBand\fP1\.2\.2\fBsatisfies\fP^1\.1\.1`\. -.SS Tilde Dependencies -.P -However, if \fBapp\fP\|'s \fBpackage\.json\fP contains: -.P -.RS 2 -.nf -"dependencies": { - "dep1": "~1\.1\.1" -} -.fi -.RE -.P -In this case, running \fBnpm update\fP will install \fB\|\. Even though the\fPlatest\fBtag points to\fP1\.2\.2\fB, this version does not satisfy\fP~1\.1\.1\fB, which is equivalent -to\fP>=1\.1\.1 <1\.2\.0\fB\|\. So the highest\-sorting version that satisfies\fP~1\.1\.1\fBis used, -which is\fP1\.1\.2`\. -.SS Caret Dependencies below 1\.0\.0 -.P -Suppose \fBapp\fP has a caret dependency on a version below \fB1\.0\.0\fP, for example: -.P -.RS 2 -.nf -"dependencies": { - "dep1": "^0\.2\.0" -} -.fi -.RE -.P -\fBnpm update\fP will install \fB, because there are no other -versions which satisfy\fP^0\.2\.0`\. -.P -If the dependence were on \fB^0\.4\.0\fP: -.P -.RS 2 -.nf -"dependencies": { - "dep1": "^0\.4\.0" -} -.fi -.RE -.P -Then \fBnpm update\fP will install \fB, because that is the highest\-sorting -version that satisfies\fP^0\.4\.0\fB(\fP>= 0\.4\.0 <0\.5\.0`) -.SS Updating Globally\-Installed Packages -.P -\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\fP, it will -be \fIdowngraded\fR\|\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help outdated -.IP \(bu 2 -npm help shrinkwrap -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help 5 folders -.IP \(bu 2 -npm help ls - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-version.1 b/deps/node/deps/npm/man/man1/npm-version.1 deleted file mode 100644 index bae79b58..00000000 --- a/deps/node/deps/npm/man/man1/npm-version.1 +++ /dev/null @@ -1,162 +0,0 @@ -.TH "NPM\-VERSION" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-version\fR \- Bump a package version -.SH SYNOPSIS -.P -.RS 2 -.nf -npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease [\-\-preid=<prerelease\-id>] | from\-git] - -\|'npm [\-v | \-\-version]' to print npm version -\|'npm view <pkg> version' to view a package's published version -\|'npm ls' to inspect current package/dependency versions -.fi -.RE -.SH DESCRIPTION -.P -Run this in a package directory to bump the version and write the new -data back to \fBpackage\.json\fP, \fBpackage\-lock\.json\fP, and, if present, \fBnpm\-shrinkwrap\.json\fP\|\. -.P -The \fBnewversion\fP argument should be a valid semver string, a -valid second argument to semver\.inc \fIhttps://github\.com/npm/node\-semver#functions\fR (one of \fBpatch\fP, \fBminor\fP, \fBmajor\fP, -\fBprepatch\fP, \fBpreminor\fP, \fBpremajor\fP, \fBprerelease\fP), or \fBfrom\-git\fP\|\. In the second case, -the existing version will be incremented by 1 in the specified field\. -\fBfrom\-git\fP will try to read the latest git tag, and use that as the new npm version\. -.P -If run in a git repo, it will also create a version commit and tag\. -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\-f\fP or -\fB\-\-force\fP flag is set\. -.P -If supplied with \fB\-m\fP or \fB\-\-message\fP config option, npm will -use it as a commit message when creating a version commit\. If the -\fBmessage\fP config contains \fB%s\fP then that will be replaced with the -resulting version number\. For example: -.P -.RS 2 -.nf -npm version patch \-m "Upgrade to %s for reasons" -.fi -.RE -.P -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 -.nf -$ npm config set sign\-git\-tag true -$ npm version patch - -You need a passphrase to unlock the secret key for -user: "isaacs (http://blog\.izs\.me/) <i@izs\.me>" -2048\-bit RSA key, ID 6C481CF6, created 2010\-08\-31 - -Enter passphrase: -.fi -.RE -.P -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\fP flag is set\. -.IP 2. 3 -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\fP\|\. -.IP 3. 3 -Bump \fBversion\fP in \fBpackage\.json\fP as requested (\fBpatch\fP, \fBminor\fP, \fBmajor\fP, etc)\. -.IP 4. 3 -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\fP\|\. -.IP 5. 3 -Commit and tag\. -.IP 6. 3 -Run the \fBpostversion\fP script\. Use it to clean up the file system or automatically push -the commit and/or tag\. - -.RE -.P -Take the following example: -.P -.RS 2 -.nf -"scripts": { - "preversion": "npm test", - "version": "npm run build && git add \-A dist", - "postversion": "git push && git push \-\-tags && rm \-rf build/temp" -} -.fi -.RE -.P -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 allow\-same\-version -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Prevents throwing an error when \fBnpm version\fP is used to set the new version -to the same value as the current version\. -.SS git\-tag\-version -.RS 0 -.IP \(bu 2 -Default: true -.IP \(bu 2 -Type: Boolean - -.RE -.P -Commit and tag the version change\. -.SS commit\-hooks -.RS 0 -.IP \(bu 2 -Default: true -.IP \(bu 2 -Type: Boolean - -.RE -.P -Run git commit hooks when committing the version change\. -.SS sign\-git\-tag -.RS 0 -.IP \(bu 2 -Default: false -.IP \(bu 2 -Type: Boolean - -.RE -.P -Pass the \fB\-s\fP flag to git to sign the tag\. -.P -Note that you must have a default GPG key set up in your git config for this to work properly\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help init -.IP \(bu 2 -npm help run\-script -.IP \(bu 2 -npm help 7 scripts -.IP \(bu 2 -npm help 5 package\.json -.IP \(bu 2 -npm help 7 semver -.IP \(bu 2 -npm help 7 config - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-view.1 b/deps/node/deps/npm/man/man1/npm-view.1 deleted file mode 100644 index 713de6e3..00000000 --- a/deps/node/deps/npm/man/man1/npm-view.1 +++ /dev/null @@ -1,146 +0,0 @@ -.TH "NPM\-VIEW" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-view\fR \- View registry info -.SH SYNOPSIS -.P -.RS 2 -.nf -npm view [<@scope>/]<name>[@<version>] [<field>[\.<subfield>]\.\.\.] - -aliases: info, show, v -.fi -.RE -.SH DESCRIPTION -.P -This command shows data about a package and prints it to the stream -referenced by the \fBoutfd\fP config, which defaults to stdout\. -.P -To show the package registry entry for the \fBconnect\fP package, you can do -this: -.P -.RS 2 -.nf -npm view connect -.fi -.RE -.P -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\fP package at version -0\.3\.5, you could do the following: -.P -.RS 2 -.nf -npm view ronn@0\.3\.5 dependencies -.fi -.RE -.P -You can view child fields by separating them with a period\. -To view the git repository URL for the latest version of npm, you could -do this: -.P -.RS 2 -.nf -npm view npm repository\.url -.fi -.RE -.P -This makes it easy to view information about a dependency with a bit of -shell scripting\. For example, to view all the data about the version of -opts that ronn depends on, you can do this: -.P -.RS 2 -.nf -npm view opts@$(npm view ronn dependencies\.opts) -.fi -.RE -.P -For fields that are arrays, requesting a non\-numeric field will return -all of the values from the objects in the list\. For example, to get all -the contributor names for the "express" project, you can do this: -.P -.RS 2 -.nf -npm view express contributors\.email -.fi -.RE -.P -You may also use numeric indices in square braces to specifically select -an item in an array field\. To just get the email address of the first -contributor in the list, you can do this: -.P -.RS 2 -.nf -npm view express contributors[0]\.email -.fi -.RE -.P -Multiple fields may be specified, and will be printed one after another\. -For example, to get all the contributor names and email addresses, you -can do this: -.P -.RS 2 -.nf -npm view express contributors\.name contributors\.email -.fi -.RE -.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\fP for more on this\.) -.P -.RS 2 -.nf -npm view npm contributors -.fi -.RE -.P -If a version range is provided, then data will be printed for every -matching version of the package\. This will show which version of jsdom -was required by each matching version of yui3: -.P -.RS 2 -.nf -npm view yui3@'>0\.5\.4' dependencies\.jsdom -.fi -.RE -.P -To show the \fBconnect\fP package version history, you can do -this: -.P -.RS 2 -.nf -npm view connect versions -.fi -.RE -.SH OUTPUT -.P -If only a single string field for a single version is output, then it -will not be colorized or quoted, so as to enable piping the output to -another command\. If the field is an object, it will be output as a JavaScript object literal\. -.P -If the \-\-json flag is given, the outputted fields will be JSON\. -.P -If the version range matches multiple versions, than each printed value -will be prefixed with the version it applies to\. -.P -If multiple fields are requested, than each of them are prefixed with -the field name\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help search -.IP \(bu 2 -npm help 7 registry -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help docs - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm-whoami.1 b/deps/node/deps/npm/man/man1/npm-whoami.1 deleted file mode 100644 index 08f23ddf..00000000 --- a/deps/node/deps/npm/man/man1/npm-whoami.1 +++ /dev/null @@ -1,26 +0,0 @@ -.TH "NPM\-WHOAMI" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm-whoami\fR \- Display npm username -.SH SYNOPSIS -.P -.RS 2 -.nf -npm whoami [\-\-registry <registry>] -.fi -.RE -.SH DESCRIPTION -.P -Print the \fBusername\fP config to standard output\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help adduser - -.RE - diff --git a/deps/node/deps/npm/man/man1/npm.1 b/deps/node/deps/npm/man/man1/npm.1 deleted file mode 100644 index 38cf7686..00000000 --- a/deps/node/deps/npm/man/man1/npm.1 +++ /dev/null @@ -1,194 +0,0 @@ -.TH "NPM" "1" "January 2019" "" "" -.SH "NAME" -\fBnpm\fR \- javascript package manager -.SH SYNOPSIS -.P -.RS 2 -.nf -npm <command> [args] -.fi -.RE -.SH VERSION -.P -6.7.0 -.SH DESCRIPTION -.P -npm is the package manager for the Node JavaScript platform\. It puts -modules in place so that node can find them, and manages dependency -conflicts intelligently\. -.P -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\fP to get a list of available commands\. -.SH IMPORTANT -.P -npm is configured to use npm, Inc\.'s public registry at -https:// by default\. Use of the npm public registry is -subject to terms of use available at https:// -.P -You can configure npm to use any compatible registry you like, and even run -your own registry\. Use of someone else's registry may be governed by their -terms of use\. -.SH INTRODUCTION -.P -You probably got npm because you want to install stuff\. -.P -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\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 -on a preinstalled git\. -.P -If one of the packages npm tries to install is a native node module and -requires compiling of C++ Code, npm will use -node\-gyp \fIhttps://github\.com/TooTallNate/node\-gyp\fR for that task\. -For a Unix system, node\-gyp \fIhttps://github\.com/TooTallNate/node\-gyp\fR -needs Python, make and a buildchain like GCC\. On Windows, -Python and Microsoft Visual Studio C++ are needed\. Python 3 is -not supported by node\-gyp \fIhttps://github\.com/TooTallNate/node\-gyp\fR\|\. -For more information visit -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\fP to learn about where npm puts stuff\. -.P -In particular, npm has two modes of operation: -.RS 0 -.IP \(bu 2 -global mode: -npm installs packages into the install prefix at -\fBprefix/lib/node_modules\fP and bins are installed in \fBprefix/bin\fP\|\. -.IP \(bu 2 -local mode: -npm installs packages into the current project directory, which -defaults to the current working directory\. Packages are installed to -\fB\|\./node_modules\fP, and bins are installed to \fB\|\./node_modules/\.bin\fP\|\. - -.RE -.P -Local mode is the default\. Use \fB\-g\fP or \fB\-\-global\fP on any command to -operate in global mode instead\. -.SH DEVELOPER USAGE -.P -If you're using npm to develop and publish your code, check out the -following help topics: -.RS 0 -.IP \(bu 2 -json: -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\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\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\fP command to upload your code to the registry\. - -.RE -.SH CONFIGURATION -.P -npm is extremely configurable\. It reads its configuration options from -5 places\. -.RS 0 -.IP \(bu 2 -Command line switches: -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\fP\|\. -.IP \(bu 2 -Environment Variables: -Set any config by prefixing the name in an environment variable with -\fBnpm_config_\fP\|\. For example, \fBexport npm_config_key=val\fP\|\. -.IP \(bu 2 -User Configs: -The file at $HOME/\.npmrc is an ini\-formatted list of configs\. If -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: -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\fP option is set in the cli, env, or user config, -then that file is parsed instead\. -.IP \(bu 2 -Defaults: -npm's default configuration options are defined in -lib/utils/config\-defs\.js\. These must not be changed\. - -.RE -.P -See npm help 7 \fBnpm\-config\fP for much much more information\. -.SH CONTRIBUTIONS -.P -Patches welcome! -.P -If you would like to contribute, but don't know what to work on, read -the contributing guidelines and check the issues list\. -.RS 0 -.IP \(bu 2 -CONTRIBUTING\.md \fIhttps://github\.com/npm/cli/blob/latest/CONTRIBUTING\.md\fR -.IP \(bu 2 -Bug tracker \fIhttps://npm\.community/c/bugs\fR -.IP \(bu 2 -Support tracker \fIhttps://npm\.community/c/support\fR - -.RE -.SH BUGS -.P -When you find issues, please report them: -.RS 0 -.IP \(bu 2 -web: -https://npm\.community/c/bugs - -.RE -.P -Be sure to follow the template and bug reporting guidelines\. You can also ask -for help in the support forum \fIhttps://npm\.community/c/support\fR if you're -unsure if it's actually a bug or are having trouble coming up with a detailed -reproduction to report\. -.SH AUTHOR -.P -Isaac Z\. Schlueter \fIhttp://blog\.izs\.me/\fR :: -isaacs \fIhttps://github\.com/isaacs/\fR :: -@izs \fIhttps://twitter\.com/izs\fR :: -i@izs\.me -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -npm help help -.IP \(bu 2 -README -.IP \(bu 2 -npm help 5 package\.json -.IP \(bu 2 -npm help install -.IP \(bu 2 -npm help config -.IP \(bu 2 -npm help 7 config -.IP \(bu 2 -npm help 5 npmrc -.IP \(bu 2 -npm help 7 index - -.RE - diff --git a/deps/node/deps/npm/man/man1/npx.1 b/deps/node/deps/npm/man/man1/npx.1 deleted file mode 100644 index d00c489c..00000000 --- a/deps/node/deps/npm/man/man1/npx.1 +++ /dev/null @@ -1,174 +0,0 @@ -.TH "NPX" "1" "April 2018" "npx@10.1.1" "User Commands" -.SH "NAME" -\fBnpx\fR \- execute npm package binaries -.SH SYNOPSIS -.P -\fBnpx [options] <command>[@version] [command\-arg]\.\.\.\fP -.P -\fBnpx [options] [\-p|\-\-package <pkg>]\.\.\. <command> [command\-arg]\.\.\.\fP -.P -\fBnpx [options] \-c '<command\-string>'\fP -.P -\fBnpx \-\-shell\-auto\-fallback [shell]\fP -.SH INSTALL -.P -\fBnpm install \-g npx\fP -.SH DESCRIPTION -.P -Executes \fB<command>\fP either from a local \fBnode_modules/\.bin\fP, or from a central cache, installing any packages needed in order for \fB<command>\fP to run\. -.P -By default, \fBnpx\fP will check whether \fB<command>\fP exists in \fB$PATH\fP, or in the local project binaries, and execute that\. If \fB<command>\fP is not found, it will be installed prior to execution\. -.P -Unless a \fB\-\-package\fP option is specified, \fBnpx\fP will try to guess the name of the binary to invoke depending on the specifier provided\. All package specifiers understood by \fBnpm\fP may be used with \fBnpx\fP, including git specifiers, remote tarballs, local directories, or scoped packages\. -.P -If a full specifier is included, or if \fB\-\-package\fP is used, npx will always use a freshly\-installed, temporary version of the package\. This can also be forced with the \fB\-\-ignore\-existing\fP flag\. -.RS 0 -.IP \(bu 2 -\fB\-p, \-\-package <package>\fP \- define the package to be installed\. This defaults to the value of \fB<command>\fP\|\. This is only needed for packages with multiple binaries if you want to call one of the other executables, or where the binary name does not match the package name\. If this option is provided \fB<command>\fP will be executed as\-is, without interpreting \fB@version\fP if it's there\. Multiple \fB\-\-package\fP options may be provided, and all the packages specified will be installed\. -.IP \(bu 2 -\fB\-\-no\-install\fP \- If passed to \fBnpx\fP, it will only try to run \fB<command>\fP if it already exists in the current path or in \fB$prefix/node_modules/\.bin\fP\|\. It won't try to install missing commands\. -.IP \(bu 2 -\fB\-\-cache <path>\fP \- set the location of the npm cache\. Defaults to npm's own cache settings\. -.IP \(bu 2 -\fB\-\-userconfig <path>\fP \- path to the user configuration file to pass to npm\. Defaults to whatever npm's current default is\. -.IP \(bu 2 -\fB\-c <string>\fP \- Execute \fB<string>\fP inside an \fBnpm run\-script\fP\-like shell environment, with all the usual environment variables available\. Only the first item in \fB<string>\fP will be automatically used as \fB<command>\fP\|\. Any others \fImust\fR use \fB\-p\fP\|\. -.IP \(bu 2 -\fB\-\-shell <string>\fP \- The shell to invoke the command with, if any\. -.IP \(bu 2 -\fB\-\-shell\-auto\-fallback [<shell>]\fP \- Generates shell code to override your shell's "command not found" handler with one that calls \fBnpx\fP\|\. Tries to figure out your shell, or you can pass its name (either \fBbash\fP, \fBfish\fP, or \fBzsh\fP) as an option\. See below for how to install\. -.IP \(bu 2 -\fB\-\-ignore\-existing\fP \- If this flag is set, npx will not look in \fB$PATH\fP, or in the current package's \fBnode_modules/\.bin\fP for an existing version before deciding whether to install\. Binaries in those paths will still be available for execution, but will be shadowed by any packages requested by this install\. -.IP \(bu 2 -\fB\-q, \-\-quiet\fP \- Suppressed any output from npx itself (progress bars, error messages, install reports)\. Subcommand output itself will not be silenced\. -.IP \(bu 2 -\fB\-n, \-\-node\-arg\fP \- Extra node argument to supply to node when binary is a node script\. You can supply this option multiple times to add more arguments\. -.IP \(bu 2 -\fB\-v, \-\-version\fP \- Show the current npx version\. - -.RE -.SH EXAMPLES -.SS Running a project\-local bin -.P -.RS 2 -.nf -$ npm i \-D webpack -$ npx webpack \.\.\. -.fi -.RE -.SS One\-off invocation without local installation -.P -.RS 2 -.nf -$ npm rm webpack -$ npx webpack \-\- \.\.\. -$ cat package\.json -\|\.\.\.webpack not in "devDependencies"\.\.\. -.fi -.RE -.SS Invoking a command from a github repository -.P -.RS 2 -.nf -$ npx github:piuccio/cowsay -\|\.\.\.or\.\.\. -$ npx git+ssh://my\.hosted\.git:cowsay\.git#semver:^1 -\|\.\.\.etc\.\.\. -.fi -.RE -.SS Execute a full shell command using one npx call w/ multiple packages -.P -.RS 2 -.nf -$ npx \-p lolcatjs \-p cowsay \-c \\ - 'echo "$npm_package_name@$npm_package_version" | cowsay | lolcatjs' -\|\.\.\. - _____ -< your\-cool\-package@1\.2\.3 > - \-\-\-\-\- - \\ ^__^ - \\ (oo)\\_______ - (__)\\ )\\/\\ - ||\-\-\-\-w | - || || -.fi -.RE -.SS Run node binary with \-\-inspect -.P -.RS 2 -.nf -$ npx \-\-node\-arg=\-\-inspect cowsay -Debugger listening on ws://127\.0\.0\.1:9229/\.\.\.\. -.fi -.RE -.SS Specify a node version to run npm scripts (or anything else!) -.P -.RS 2 -.nf -npx \-p node@8 npm run build -.fi -.RE -.SH SHELL AUTO FALLBACK -.P -You can configure \fBnpx\fP to run as your default fallback command when you type something in the command line with an \fB@\fP but the command is not found\. This includes installing packages that were not found in the local prefix either\. -.P -For example: -.P -.RS 2 -.nf -$ npm@4 \-\-version -(stderr) npm@4 not found\. Trying with npx\.\.\. -4\.6\.1 -$ asdfasdfasf -zsh: command not found: asfdasdfasdf -.fi -.RE -.P -Currently, \fBzsh\fP, \fBbash\fP (>= 4), and \fBfish\fP are supported\. You can access these completion scripts using \fBnpx \-\-shell\-auto\-fallback <shell>\fP\|\. -.P -To install permanently, add the relevant line below to your \fB~/\.bashrc\fP, \fB~/\.zshrc\fP, \fB~/\.config/fish/config\.fish\fP, or as needed\. To install just for the shell session, simply run the line\. -.P -You can optionally pass through \fB\-\-no\-install\fP when generating the fallback to prevent it from installing packages if the command is missing\. -.SS For bash@>=4: -.P -.RS 2 -.nf -$ source <(npx \-\-shell\-auto\-fallback bash) -.fi -.RE -.SS For zsh: -.P -.RS 2 -.nf -$ source <(npx \-\-shell\-auto\-fallback zsh) -.fi -.RE -.SS For fish: -.P -.RS 2 -.nf -$ source (npx \-\-shell\-auto\-fallback fish | psub) -.fi -.RE -.SH ACKNOWLEDGEMENTS -.P -Huge thanks to Kwyn Meagher \fIhttps://blog\.kwyn\.io\fR for generously donating the package name in the main npm registry\. Previously \fBnpx\fP was used for a Tessel board Neopixels library, which can now be found under \fBnpx\-tessel\fP \fIhttps://npm\.im/npx\-tessel\fR\|\. -.SH AUTHOR -.P -Written by Kat Marchan \fIhttps://github\.com/zkat\fR\|\. -.SH REPORTING BUGS -.P -Please file any relevant issues on Github\. \fIhttps://github\.com/zkat/npx\fR -.SH LICENSE -.P -This work is released by its authors into the public domain under CC0\-1\.0\. See \fBLICENSE\.md\fP for details\. -.SH SEE ALSO -.RS 0 -.IP \(bu 2 -\fBnpm(1)\fP -.IP \(bu 2 -\fBnpm\-run\-script(1)\fP -.IP \(bu 2 -\fBnpm\-config(7)\fP - -.RE |