@surgeapi/node 0.30.0 → 0.31.0

package/oidc/node_modules/npm/man/man1/npm-pack.1

@@ -1,143 +0,0 @@
-.TH "NPM-PACK" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-pack\fR - Create a tarball from a package
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm pack <package-spec>
-.fi
-.RE
-.SS "Configuration"
-.SS "\fBdry-run\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Indicates that you don't want npm to make any changes and that it should only report what it would have done. This can be passed into any of the commands that modify your local installation, eg, \fBinstall\fR, \fBupdate\fR, \fBdedupe\fR, \fBuninstall\fR, as well as \fBpack\fR and \fBpublish\fR.
-.P
-Note: This is NOT honored by other network related commands, eg \fBdist-tags\fR, \fBowner\fR, etc.
-.SS "\fBjson\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Whether or not to output JSON data, rather than the normal output.
-.RS 0
-.IP \(bu 4
-In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.
-.RE 0
-
-.P
-Not supported by all npm commands.
-.SS "\fBpack-destination\fR"
-.RS 0
-.IP \(bu 4
-Default: "."
-.IP \(bu 4
-Type: String
-.RE 0
-
-.P
-Directory in which \fBnpm pack\fR will save tarballs.
-.SS "\fBworkspace\fR"
-.RS 0
-.IP \(bu 4
-Default:
-.IP \(bu 4
-Type: String (can be set multiple times)
-.RE 0
-
-.P
-Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option.
-.P
-Valid values for the \fBworkspace\fR config are either:
-.RS 0
-.IP \(bu 4
-Workspace names
-.IP \(bu 4
-Path to a workspace directory
-.IP \(bu 4
-Path to a parent workspace directory (will result in selecting all workspaces within that folder)
-.RE 0
-
-.P
-When set for the \fBnpm init\fR command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.
-.P
-This value is not exported to the environment for child processes.
-.SS "\fBworkspaces\fR"
-.RS 0
-.IP \(bu 4
-Default: null
-.IP \(bu 4
-Type: null or Boolean
-.RE 0
-
-.P
-Set to true to run the command in the context of \fBall\fR configured workspaces.
-.P
-Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:
-.RS 0
-.IP \(bu 4
-Commands that operate on the \fBnode_modules\fR tree (install, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, \fIunless\fR one or more workspaces are specified in the \fBworkspace\fR config.
-.RE 0
-
-.P
-This value is not exported to the environment for child processes.
-.SS "\fBinclude-workspace-root\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Include the workspace root when workspaces are enabled for a command.
-.P
-When false, specifying individual workspaces via the \fBworkspace\fR config, or all workspaces via the \fBworkspaces\fR flag, will cause npm to operate only on the specified workspaces, and not on the root project.
-.P
-This value is not exported to the environment for child processes.
-.SS "\fBignore-scripts\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-If true, npm does not run scripts specified in package.json files.
-.P
-Note that commands explicitly intended to run a particular script, such as \fBnpm start\fR, \fBnpm stop\fR, \fBnpm restart\fR, \fBnpm test\fR, and \fBnpm
-run\fR will still run their intended script if \fBignore-scripts\fR is set, but they will \fInot\fR run any pre- or post-scripts.
-.SS "Description"
-.P
-For anything that's installable (that is, a package folder, tarball, tarball url, git url, name@tag, name@version, name, or scoped name), this command will fetch it to the cache, copy the tarball to the current working directory as \fB<name>-<version>.tgz\fR, 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.
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help "package spec"
-.IP \(bu 4
-\fBnpm-packlist package\fR \fI\(lahttp://npm.im/npm-packlist\(ra\fR
-.IP \(bu 4
-npm help cache
-.IP \(bu 4
-npm help publish
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help npmrc
-.RE 0

package/oidc/node_modules/npm/man/man1/npm-ping.1

@@ -1,52 +0,0 @@
-.TH "NPM-PING" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-ping\fR - Ping npm registry
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm ping
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "Description"
-.P
-Ping the configured or given npm registry and verify authentication. If it works it will output something like:
-.P
-.RS 2
-.nf
-npm notice PING https://registry.npmjs.org/
-npm notice PONG 255ms
-.fi
-.RE
-.P
-otherwise you will get an error:
-.P
-.RS 2
-.nf
-npm notice PING http://foo.com/
-npm ERR! code E404
-npm ERR! 404 Not Found - GET http://www.foo.com/-/ping?write=true
-.fi
-.RE
-.SS "Configuration"
-.SS "\fBregistry\fR"
-.RS 0
-.IP \(bu 4
-Default: "https://registry.npmjs.org/"
-.IP \(bu 4
-Type: URL
-.RE 0
-
-.P
-The base URL of the npm registry.
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help doctor
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help npmrc
-.RE 0

package/oidc/node_modules/npm/man/man1/npm-pkg.1

@@ -1,286 +0,0 @@
-.TH "NPM-PKG" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-pkg\fR - Manages your package.json
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm pkg set <key>=<value> \[lB]<key>=<value> ...\[rB]
-npm pkg get \[lB]<key> \[lB]<key> ...\[rB]\[rB]
-npm pkg delete <key> \[lB]<key> ...\[rB]
-npm pkg set \[lB]<array>\[lB]<index>\[rB].<key>=<value> ...\[rB]
-npm pkg set \[lB]<array>\[lB]\[rB].<key>=<value> ...\[rB]
-npm pkg fix
-.fi
-.RE
-.SS "Description"
-.P
-A command that automates the management of \fBpackage.json\fR files. \fBnpm pkg\fR provide 3 different sub commands that allow you to modify or retrieve values for given object keys in your \fBpackage.json\fR.
-.P
-The syntax to retrieve and set fields is a dot separated representation of the nested object properties to be found within your \fBpackage.json\fR, it's the same notation used in npm help view to retrieve information from the registry manifest, below you can find more examples on how to use it.
-.P
-Returned values are always in \fBjson\fR format.
-.RS 0
-.IP \(bu 4
-\fBnpm pkg get <field>\fR
-.P
-Retrieves a value \fBkey\fR, defined in your \fBpackage.json\fR file.
-.P
-For example, in order to retrieve the name of the current package, you can run:
-.P
-.RS 2
-.nf
-npm pkg get name
-.fi
-.RE
-.P
-It's also possible to retrieve multiple values at once:
-.P
-.RS 2
-.nf
-npm pkg get name version
-.fi
-.RE
-.P
-You can view child fields by separating them with a period. To retrieve the value of a test \fBscript\fR value, you would run the following command:
-.P
-.RS 2
-.nf
-npm pkg get scripts.test
-.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 emails for a package, you would run:
-.P
-.RS 2
-.nf
-npm pkg get 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 run:
-.P
-.RS 2
-.nf
-npm pkg get contributors\[lB]0\[rB].email
-.fi
-.RE
-.P
-For complex fields you can also name a property in square brackets to specifically select a child field. This is especially helpful with the exports object:
-.P
-.RS 2
-.nf
-npm pkg get "exports\[lB].\[rB].require"
-.fi
-.RE
-.IP \(bu 4
-\fBnpm pkg set <field>=<value>\fR
-.P
-Sets a \fBvalue\fR in your \fBpackage.json\fR based on the \fBfield\fR value. When saving to your \fBpackage.json\fR file the same set of rules used during \fBnpm install\fR and other cli commands that touches the \fBpackage.json\fR file are used, making sure to respect the existing indentation and possibly applying some validation prior to saving values to the file.
-.P
-The same syntax used to retrieve values from your package can also be used to define new properties or overriding existing ones, below are some examples of how the dot separated syntax can be used to edit your \fBpackage.json\fR file.
-.P
-Defining a new bin named \fBmynewcommand\fR in your \fBpackage.json\fR that points to a file \fBcli.js\fR:
-.P
-.RS 2
-.nf
-npm pkg set bin.mynewcommand=cli.js
-.fi
-.RE
-.P
-Setting multiple fields at once is also possible:
-.P
-.RS 2
-.nf
-npm pkg set description='Awesome package' engines.node='>=10'
-.fi
-.RE
-.P
-It's also possible to add to array values, for example to add a new contributor entry:
-.P
-.RS 2
-.nf
-npm pkg set contributors\[lB]0\[rB].name='Foo' contributors\[lB]0\[rB].email='foo@bar.ca'
-.fi
-.RE
-.P
-You may also append items to the end of an array using the special empty bracket notation:
-.P
-.RS 2
-.nf
-npm pkg set contributors\[lB]\[rB].name='Foo' contributors\[lB]\[rB].name='Bar'
-.fi
-.RE
-.P
-It's also possible to parse values as json prior to saving them to your \fBpackage.json\fR file, for example in order to set a \fB"private": true\fR property:
-.P
-.RS 2
-.nf
-npm pkg set private=true --json
-.fi
-.RE
-.P
-It also enables saving values as numbers:
-.P
-.RS 2
-.nf
-npm pkg set tap.timeout=60 --json
-.fi
-.RE
-.IP \(bu 4
-\fBnpm pkg delete <key>\fR
-.P
-Deletes a \fBkey\fR from your \fBpackage.json\fR
-.P
-The same syntax used to set values from your package can also be used to remove existing ones. For example, in order to remove a script named build:
-.P
-.RS 2
-.nf
-npm pkg delete scripts.build
-.fi
-.RE
-.IP \(bu 4
-\fBnpm pkg fix\fR
-.P
-Auto corrects common errors in your \fBpackage.json\fR. npm already does this during \fBpublish\fR, which leads to subtle (mostly harmless) differences between the contents of your \fBpackage.json\fR file and the manifest that npm uses during installation.
-.RE 0
-
-.SS "Workspaces support"
-.P
-You can set/get/delete items across your configured workspaces by using the \fB\[rs]fBworkspace\[rs]fR\fR \fI\(la/using-npm/config#workspace\(ra\fR or \fB\[rs]fBworkspaces\[rs]fR\fR \fI\(la/using-npm/config#workspaces\(ra\fR config options.
-.P
-For example, setting a \fBfunding\fR value across all configured workspaces of a project:
-.P
-.RS 2
-.nf
-npm pkg set funding=https://example.com --ws
-.fi
-.RE
-.P
-When using \fBnpm pkg get\fR to retrieve info from your configured workspaces, the returned result will be in a json format in which top level keys are the names of each workspace, the values of these keys will be the result values returned from each of the configured workspaces, e.g:
-.P
-.RS 2
-.nf
-npm pkg get name version --ws
-{
-  "a": {
-    "name": "a",
-    "version": "1.0.0"
-  },
-  "b": {
-    "name": "b",
-    "version": "1.0.0"
-  }
-}
-.fi
-.RE
-.SS "Configuration"
-.SS "\fBforce\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Removes various protections against unfortunate side effects, common mistakes, unnecessary performance degradation, and malicious input.
-.RS 0
-.IP \(bu 4
-Allow clobbering non-npm files in global installs.
-.IP \(bu 4
-Allow the \fBnpm version\fR command to work on an unclean git repository.
-.IP \(bu 4
-Allow deleting the cache folder with \fBnpm cache clean\fR.
-.IP \(bu 4
-Allow installing packages that have an \fBengines\fR declaration requiring a different version of npm.
-.IP \(bu 4
-Allow installing packages that have an \fBengines\fR declaration requiring a different version of \fBnode\fR, even if \fB--engine-strict\fR is enabled.
-.IP \(bu 4
-Allow \fBnpm audit fix\fR to install modules outside your stated dependency range (including SemVer-major changes).
-.IP \(bu 4
-Allow unpublishing all versions of a published package.
-.IP \(bu 4
-Allow conflicting peerDependencies to be installed in the root project.
-.IP \(bu 4
-Implicitly set \fB--yes\fR during \fBnpm init\fR.
-.IP \(bu 4
-Allow clobbering existing values in \fBnpm pkg\fR
-.IP \(bu 4
-Allow unpublishing of entire packages (not just a single version).
-.RE 0
-
-.P
-If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option!
-.SS "\fBjson\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Whether or not to output JSON data, rather than the normal output.
-.RS 0
-.IP \(bu 4
-In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.
-.RE 0
-
-.P
-Not supported by all npm commands.
-.SS "\fBworkspace\fR"
-.RS 0
-.IP \(bu 4
-Default:
-.IP \(bu 4
-Type: String (can be set multiple times)
-.RE 0
-
-.P
-Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option.
-.P
-Valid values for the \fBworkspace\fR config are either:
-.RS 0
-.IP \(bu 4
-Workspace names
-.IP \(bu 4
-Path to a workspace directory
-.IP \(bu 4
-Path to a parent workspace directory (will result in selecting all workspaces within that folder)
-.RE 0
-
-.P
-When set for the \fBnpm init\fR command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.
-.P
-This value is not exported to the environment for child processes.
-.SS "\fBworkspaces\fR"
-.RS 0
-.IP \(bu 4
-Default: null
-.IP \(bu 4
-Type: null or Boolean
-.RE 0
-
-.P
-Set to true to run the command in the context of \fBall\fR configured workspaces.
-.P
-Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:
-.RS 0
-.IP \(bu 4
-Commands that operate on the \fBnode_modules\fR tree (install, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, \fIunless\fR one or more workspaces are specified in the \fBworkspace\fR config.
-.RE 0
-
-.P
-This value is not exported to the environment for child processes.
-.SH "SEE ALSO"
-.RS 0
-.IP \(bu 4
-npm help install
-.IP \(bu 4
-npm help init
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help workspaces
-.RE 0

package/oidc/node_modules/npm/man/man1/npm-prefix.1

@@ -1,63 +0,0 @@
-.TH "NPM-PREFIX" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-prefix\fR - Display prefix
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm prefix
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "Description"
-.P
-Print the local prefix to standard output. This is the closest parent directory to contain a \fBpackage.json\fR file or \fBnode_modules\fR directory, unless \fB-g\fR is also specified.
-.P
-If \fB-g\fR is specified, this will be the value of the global prefix. See npm help config for more detail.
-.SS "Example"
-.P
-.RS 2
-.nf
-npm prefix
-/usr/local/projects/foo
-.fi
-.RE
-.P
-.RS 2
-.nf
-npm prefix -g
-/usr/local
-.fi
-.RE
-.SS "Configuration"
-.SS "\fBglobal\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Operates in "global" mode, so that packages are installed into the \fBprefix\fR folder instead of the current working directory. See npm help folders for more on the differences in behavior.
-.RS 0
-.IP \(bu 4
-packages are installed into the \fB{prefix}/lib/node_modules\fR folder, instead of the current working directory.
-.IP \(bu 4
-bin files are linked to \fB{prefix}/bin\fR
-.IP \(bu 4
-man pages are linked to \fB{prefix}/share/man\fR
-.RE 0
-
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help root
-.IP \(bu 4
-npm help folders
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help npmrc
-.RE 0

package/oidc/node_modules/npm/man/man1/npm-profile.1

@@ -1,127 +0,0 @@
-.TH "NPM-PROFILE" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-profile\fR - Change settings on your registry profile
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm profile enable-2fa \[lB]auth-only|auth-and-writes\[rB]
-npm profile disable-2fa
-npm profile get \[lB]<key>\[rB]
-npm profile set <key> <value>
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "Description"
-.P
-Change your profile information on the registry. Note that this command depends on the registry implementation, so third-party registries may not support this interface.
-.RS 0
-.IP \(bu 4
-\fBnpm profile get \[lB]<property>\[rB]\fR: Display all of the properties of your profile, or one or more specific properties. It looks like:
-.RE 0
-
-.P
-.RS 2
-.nf
-name: example
-email: e@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 4
-\fBnpm profile set <property> <value>\fR: Set the value of a profile property. You can set the following properties this way: email, fullname, homepage, freenode, twitter, github
-.IP \(bu 4
-\fBnpm profile set password\fR: 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 4
-\fBnpm profile enable-2fa \[lB]auth-and-writes|auth-only\[rB]\fR: Enables two-factor authentication. Defaults to \fBauth-and-writes\fR mode. Modes are:
-.RS 4
-.IP \(bu 4
-\fBauth-only\fR: 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 4
-\fBauth-and-writes\fR: Requires an OTP at all the times \fBauth-only\fR does, and also requires one when publishing a module, setting the \fBlatest\fR dist-tag, or changing access via \fBnpm access\fR and \fBnpm owner\fR.
-.RE 0
-
-.IP \(bu 4
-\fBnpm profile disable-2fa\fR: Disables two-factor authentication.
-.RE 0
-
-.SS "Details"
-.P
-Some of these commands may not be available on non npmjs.com registries.
-.SS "Configuration"
-.SS "\fBregistry\fR"
-.RS 0
-.IP \(bu 4
-Default: "https://registry.npmjs.org/"
-.IP \(bu 4
-Type: URL
-.RE 0
-
-.P
-The base URL of the npm registry.
-.SS "\fBjson\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Whether or not to output JSON data, rather than the normal output.
-.RS 0
-.IP \(bu 4
-In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.
-.RE 0
-
-.P
-Not supported by all npm commands.
-.SS "\fBparseable\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Output parseable results from commands that write to standard output. For \fBnpm search\fR, this will be tab-separated table format.
-.SS "\fBotp\fR"
-.RS 0
-.IP \(bu 4
-Default: null
-.IP \(bu 4
-Type: null or String
-.RE 0
-
-.P
-This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions with \fBnpm
-access\fR.
-.P
-If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help adduser
-.IP \(bu 4
-npm help registry
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help npmrc
-.IP \(bu 4
-npm help owner
-.IP \(bu 4
-npm help whoami
-.IP \(bu 4
-npm help token
-.RE 0