@surgeapi/node 0.30.0 → 0.31.0

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

@@ -1,75 +0,0 @@
-.TH "NPM-STOP" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-stop\fR - Stop a package
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm stop \[lB]-- <args>\[rB]
-.fi
-.RE
-.SS "Description"
-.P
-This runs a predefined command specified in the "stop" property of a package's "scripts" object.
-.P
-Unlike with npm help start, there is no default script that will run if the \fB"stop"\fR property is not defined.
-.SS "Example"
-.P
-.RS 2
-.nf
-{
-  "scripts": {
-    "stop": "node bar.js"
-  }
-}
-.fi
-.RE
-.P
-.RS 2
-.nf
-npm stop
-
-> npm@x.x.x stop
-> node bar.js
-
-(bar.js output would be here)
-
-.fi
-.RE
-.SS "Configuration"
-.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 "\fBscript-shell\fR"
-.RS 0
-.IP \(bu 4
-Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows
-.IP \(bu 4
-Type: null or String
-.RE 0
-
-.P
-The shell to use for scripts run with the \fBnpm exec\fR, \fBnpm run\fR and \fBnpm init <package-spec>\fR commands.
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help run
-.IP \(bu 4
-npm help scripts
-.IP \(bu 4
-npm help test
-.IP \(bu 4
-npm help start
-.IP \(bu 4
-npm help restart
-.RE 0

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

@@ -1,149 +0,0 @@
-.TH "NPM-TEAM" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-team\fR - Manage organization teams and team memberships
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm team create <scope:team> \[lB]--otp <otpcode>\[rB]
-npm team destroy <scope:team> \[lB]--otp <otpcode>\[rB]
-npm team add <scope:team> <user> \[lB]--otp <otpcode>\[rB]
-npm team rm <scope:team> <user> \[lB]--otp <otpcode>\[rB]
-npm team ls <scope>|<scope:team>
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "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:\fR). That is, if you have a \fBnewteam\fR team in an \fBorg\fR organization, you must always refer to that team as \fB@org:newteam\fR in these commands.
-.P
-If you have two-factor authentication enabled in \fBauth-and-writes\fR mode, then you can provide a code from your authenticator with \fB\[lB]--otp <otpcode>\[rB]\fR. If you don't include this then you will be taken through a second factor flow based on your \fBauthtype\fR.
-.RS 0
-.IP \(bu 4
-create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the \fBdevelopers\fR team, \fBlearn more.\fR \fI\(lahttps://docs.npmjs.com/about-developers-team\(ra\fR
-.P
-Here's how to create a new team \fBnewteam\fR under the \fBorg\fR org:
-.P
-.RS 2
-.nf
-npm team create @org:newteam
-.fi
-.RE
-.P
-You should see a confirming message such as: \fB+@org:newteam\fR once the new team has been created.
-.IP \(bu 4
-add: Add a user to an existing team.
-.P
-Adding a new user \fBusername\fR to a team named \fBnewteam\fR under the \fBorg\fR org:
-.P
-.RS 2
-.nf
-npm team add @org:newteam username
-.fi
-.RE
-.P
-On success, you should see a message: \fBusername added to @org:newteam\fR
-.IP \(bu 4
-rm: Using \fBnpm team rm\fR you can also remove users from a team they belong to.
-.P
-Here's an example removing user \fBusername\fR from \fBnewteam\fR team in \fBorg\fR organization:
-.P
-.RS 2
-.nf
-npm team rm @org:newteam username
-.fi
-.RE
-.P
-Once the user is removed a confirmation message is displayed: \fBusername removed from @org:newteam\fR
-.IP \(bu 4
-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.
-.P
-Here's an example of how to list all teams from an org named \fBorg\fR:
-.P
-.RS 2
-.nf
-npm team ls @org
-.fi
-.RE
-.P
-Example listing all members of a team named \fBnewteam\fR:
-.P
-.RS 2
-.nf
-npm team ls @org:newteam
-.fi
-.RE
-.RE 0
-
-.SS "Details"
-.P
-\fBnpm team\fR always operates directly on the current registry, configurable from the command line using \fB--registry=<registry url>\fR.
-.P
-You must be a \fIteam admin\fR to create teams and manage team membership, under the given organization. Listing teams and team memberships may be done by any member of the organization.
-.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\fR command to grant or revoke the appropriate permissions.
-.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 "\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 "\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 "\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 "See Also"
-.RS 0
-.IP \(bu 4
-npm help access
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help registry
-.RE 0

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

@@ -1,73 +0,0 @@
-.TH "NPM-TEST" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-test\fR - Test a package
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm test \[lB]-- <args>\[rB]
-
-aliases: tst, t
-.fi
-.RE
-.SS "Description"
-.P
-This runs a predefined command specified in the \fB"test"\fR property of a package's \fB"scripts"\fR object.
-.SS "Example"
-.P
-.RS 2
-.nf
-{
-  "scripts": {
-    "test": "node test.js"
-  }
-}
-.fi
-.RE
-.P
-.RS 2
-.nf
-npm test
-> npm@x.x.x test
-> node test.js
-
-(test.js output would be here)
-.fi
-.RE
-.SS "Configuration"
-.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 "\fBscript-shell\fR"
-.RS 0
-.IP \(bu 4
-Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows
-.IP \(bu 4
-Type: null or String
-.RE 0
-
-.P
-The shell to use for scripts run with the \fBnpm exec\fR, \fBnpm run\fR and \fBnpm init <package-spec>\fR commands.
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help run
-.IP \(bu 4
-npm help scripts
-.IP \(bu 4
-npm help start
-.IP \(bu 4
-npm help restart
-.IP \(bu 4
-npm help stop
-.RE 0

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

@@ -1,113 +0,0 @@
-.TH "NPM-TOKEN" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-token\fR - Manage your authentication tokens
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm token list
-npm token revoke <id|token>
-npm token create \[lB]--read-only\[rB] \[lB]--cidr=list\[rB]
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "Description"
-.P
-This lets you list, create and revoke authentication tokens.
-.RS 0
-.IP \(bu 4
-\fBnpm token list\fR: Shows a table of all active authentication tokens. You can request this as JSON with \fB--json\fR or tab-separated values with \fB--parseable\fR.
-.RE 0
-
-.P
-.RS 2
-.nf
-Read only token npm_1f… with id 7f3134 created 2017-10-21
-
-Publish token npm_af…  with id c03241 created 2017-10-02
-with IP Whitelist: 192.168.0.1/24
-
-Publish token npm_… with id e0cf92 created 2017-10-02
-
-.fi
-.RE
-.RS 0
-.IP \(bu 4
-\fBnpm token create \[lB]--read-only\[rB] \[lB]--cidr=<cidr-ranges>\[rB]\fR: Create a new authentication token. It can be \fB--read-only\fR, or accept a list of \fBCIDR\fR \fI\(lahttps://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing\(ra\fR ranges with which to limit use of this token. This will prompt you for your password, and, if you have two-factor authentication enabled, an otp.
-.P
-Currently, the cli cannot generate automation tokens. Please refer to the \fBdocs website\fR \fI\(lahttps://docs.npmjs.com/creating-and-viewing-access-tokens\(ra\fR for more information on generating automation tokens.
-.RE 0
-
-.P
-.RS 2
-.nf
-Created publish token a73c9572-f1b9-8983-983d-ba3ac3cc913d
-.fi
-.RE
-.RS 0
-.IP \(bu 4
-\fBnpm token revoke <token|id>\fR: Immediately removes an authentication token from the registry. You will no longer be able to use it. This can accept both complete tokens (such as those you get back from \fBnpm token create\fR, and those found in your \fB.npmrc\fR), and ids as seen in the parseable or json output of \fBnpm token list\fR. This will NOT accept the truncated token found in the normal \fBnpm token list\fR output.
-.RE 0
-
-.SS "Configuration"
-.SS "\fBread-only\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-This is used to mark a token as unable to publish when configuring limited access tokens with the \fBnpm token create\fR command.
-.SS "\fBcidr\fR"
-.RS 0
-.IP \(bu 4
-Default: null
-.IP \(bu 4
-Type: null or String (can be set multiple times)
-.RE 0
-
-.P
-This is a list of CIDR address to be used when configuring limited access tokens with the \fBnpm token create\fR command.
-.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 "\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 profile
-.RE 0

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

@@ -1,58 +0,0 @@
-.TH "NPM-UNDEPRECATE" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-undeprecate\fR - Undeprecate a version of a package
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm undeprecate <package-spec>
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "Description"
-.P
-This command will update the npm registry entry for a package, removing any deprecation warnings that currently exist.
-.P
-It works in the same way as npm help deprecate, except that this command removes deprecation warnings instead of adding them.
-.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 "\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 "\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 "See Also"
-.RS 0
-.IP \(bu 4
-npm help deprecate
-.RE 0

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

@@ -1,159 +0,0 @@
-.TH "NPM-UNINSTALL" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-uninstall\fR - Remove a package
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm uninstall \[lB]<@scope>/\[rB]<pkg>...
-
-aliases: unlink, remove, rm, r, un
-.fi
-.RE
-.SS "Description"
-.P
-This uninstalls a package, completely removing everything npm installed on its behalf.
-.P
-It also removes the package from the \fBdependencies\fR, \fBdevDependencies\fR, \fBoptionalDependencies\fR, and \fBpeerDependencies\fR objects in your \fBpackage.json\fR.
-.P
-Further, if you have an \fBnpm-shrinkwrap.json\fR or \fBpackage-lock.json\fR, npm will update those files as well.
-.P
-\fB--no-save\fR will tell npm not to remove the package from your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, or \fBpackage-lock.json\fR files.
-.P
-\fB--save\fR or \fB-S\fR will tell npm to remove the package from your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, and \fBpackage-lock.json\fR files. This is the default, but you may need to use this if you have for instance \fBsave=false\fR in your \fBnpmrc\fR file
-.P
-In global mode (ie, with \fB-g\fR or \fB--global\fR appended to the command), it uninstalls the current package context as a global package. \fB--no-save\fR is ignored in this case.
-.P
-Scope is optional and follows the usual rules for npm help scope.
-.SS "Examples"
-.P
-.RS 2
-.nf
-npm uninstall sax
-.fi
-.RE
-.P
-\fBsax\fR will no longer be in your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, or \fBpackage-lock.json\fR files.
-.P
-.RS 2
-.nf
-npm uninstall lodash --no-save
-.fi
-.RE
-.P
-\fBlodash\fR will not be removed from your \fBpackage.json\fR, \fBnpm-shrinkwrap.json\fR, or \fBpackage-lock.json\fR files.
-.SS "Configuration"
-.SS "\fBsave\fR"
-.RS 0
-.IP \(bu 4
-Default: \fBtrue\fR unless when using \fBnpm update\fR where it defaults to \fBfalse\fR
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Save installed packages to a \fBpackage.json\fR file as dependencies.
-.P
-When used with the \fBnpm rm\fR command, removes the dependency from \fBpackage.json\fR.
-.P
-Will also prevent writing to \fBpackage-lock.json\fR if set to \fBfalse\fR.
-.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 "\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 "\fBinstall-links\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-When set file: protocol dependencies will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help prune
-.IP \(bu 4
-npm help install
-.IP \(bu 4
-npm help folders
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help npmrc
-.RE 0