jfrog-cli-v2-jf 2.6.0

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-access.1

@@ -0,0 +1,92 @@
+.TH "NPM\-ACCESS" "1" "February 2018" "" ""
+.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 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
+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
+npm help team
+.IP \(bu 2
+npm help publish
+.IP \(bu 2
+npm help 7 config
+.IP \(bu 2
+npm help 7 registry
+
+.RE
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-adduser.1

@@ -0,0 +1,103 @@
+.TH "NPM\-ADDUSER" "1" "February 2018" "" ""
+.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://registry\.npmjs\.org/
+.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
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-bin.1

@@ -0,0 +1,30 @@
+.TH "NPM\-BIN" "1" "February 2018" "" ""
+.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
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-bugs.1

@@ -0,0 +1,60 @@
+.TH "NPM\-BUGS" "1" "February 2018" "" ""
+.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://registry\.npmjs\.org/
+.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
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-build.1

@@ -0,0 +1,41 @@
+.TH "NPM\-BUILD" "1" "February 2018" "" ""
+.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
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-bundle.1

@@ -0,0 +1,17 @@
+.TH "NPM\-BUNDLE" "1" "February 2018" "" ""
+.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
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-cache.1

@@ -0,0 +1,96 @@
+.TH "NPM\-CACHE" "1" "February 2018" "" ""
+.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://npm\.im/cacache
+.IP \(bu 2
+https://npm\.im/pacote
+
+.RE
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-completion.1

@@ -0,0 +1,42 @@
+.TH "NPM\-COMPLETION" "1" "February 2018" "" ""
+.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 npm completion to a file
+such as \fB/usr/local/etc/bash_completion\.d/npm\fP if you have a system
+that will read that file for you\.
+.P
+When \fBCOMP_CWORD\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
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-config.1

@@ -0,0 +1,97 @@
+.TH "NPM\-CONFIG" "1" "February 2018" "" ""
+.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
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-dedupe.1

@@ -0,0 +1,71 @@
+.TH "NPM\-DEDUPE" "1" "February 2018" "" ""
+.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
+

package/node-v8.11.1-linux-x64/lib/node_modules/npm/man/man1/npm-deprecate.1

@@ -0,0 +1,37 @@
+.TH "NPM\-DEPRECATE" "1" "February 2018" "" ""
+.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 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\.
+.SH SEE ALSO
+.RS 0
+.IP \(bu 2
+npm help publish
+.IP \(bu 2
+npm help 7 registry
+
+.RE
+