@surgeapi/node 0.30.0 → 0.32.0

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

@@ -1,314 +0,0 @@
-.TH "NPM-SBOM" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-sbom\fR - Generate a Software Bill of Materials (SBOM)
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm sbom
-.fi
-.RE
-.SS "Description"
-.P
-The \fBnpm sbom\fR command generates a Software Bill of Materials (SBOM) listing the dependencies for the current project. SBOMs can be generated in either \fBSPDX\fR \fI\(lahttps://spdx.dev/\(ra\fR or \fBCycloneDX\fR \fI\(lahttps://cyclonedx.org/\(ra\fR format.
-.SS "Example CycloneDX SBOM"
-.P
-.RS 2
-.nf
-{
-  "$schema": "http://cyclonedx.org/schema/bom-1.5.schema.json",
-  "bomFormat": "CycloneDX",
-  "specVersion": "1.5",
-  "serialNumber": "urn:uuid:09f55116-97e1-49cf-b3b8-44d0207e7730",
-  "version": 1,
-  "metadata": {
-    "timestamp": "2023-09-01T00:00:00.001Z",
-    "lifecycles": \[lB]
-      {
-        "phase": "build"
-      }
-    \[rB],
-    "tools": \[lB]
-      {
-        "vendor": "npm",
-        "name": "cli",
-        "version": "10.1.0"
-      }
-    \[rB],
-    "component": {
-      "bom-ref": "simple@1.0.0",
-      "type": "library",
-      "name": "simple",
-      "version": "1.0.0",
-      "scope": "required",
-      "author": "John Doe",
-      "description": "simple react app",
-      "purl": "pkg:npm/simple@1.0.0",
-      "properties": \[lB]
-        {
-          "name": "cdx:npm:package:path",
-          "value": ""
-        }
-      \[rB],
-      "externalReferences": \[lB]\[rB],
-      "licenses": \[lB]
-        {
-          "license": {
-            "id": "MIT"
-          }
-        }
-      \[rB]
-    }
-  },
-  "components": \[lB]
-    {
-      "bom-ref": "lodash@4.17.21",
-      "type": "library",
-      "name": "lodash",
-      "version": "4.17.21",
-      "scope": "required",
-      "author": "John-David Dalton",
-      "description": "Lodash modular utilities.",
-      "purl": "pkg:npm/lodash@4.17.21",
-      "properties": \[lB]
-        {
-          "name": "cdx:npm:package:path",
-          "value": "node_modules/lodash"
-        }
-      \[rB],
-      "externalReferences": \[lB]
-        {
-          "type": "distribution",
-          "url": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz"
-        },
-        {
-          "type": "vcs",
-          "url": "git+https://github.com/lodash/lodash.git"
-        },
-        {
-          "type": "website",
-          "url": "https://lodash.com/"
-        },
-        {
-          "type": "issue-tracker",
-          "url": "https://github.com/lodash/lodash/issues"
-        }
-      \[rB],
-      "hashes": \[lB]
-        {
-          "alg": "SHA-512",
-          "content": "bf690311ee7b95e713ba568322e3533f2dd1cb880b189e99d4edef13592b81764daec43e2c54c61d5c558dc5cfb35ecb85b65519e74026ff17675b6f8f916f4a"
-        }
-      \[rB],
-      "licenses": \[lB]
-        {
-          "license": {
-            "id": "MIT"
-          }
-        }
-      \[rB]
-    }
-  \[rB],
-  "dependencies": \[lB]
-    {
-      "ref": "simple@1.0.0",
-      "dependsOn": \[lB]
-        "lodash@4.17.21"
-      \[rB]
-    },
-    {
-      "ref": "lodash@4.17.21",
-      "dependsOn": \[lB]\[rB]
-    }
-  \[rB]
-}
-.fi
-.RE
-.SS "Example SPDX SBOM"
-.P
-.RS 2
-.nf
-{
-  "spdxVersion": "SPDX-2.3",
-  "dataLicense": "CC0-1.0",
-  "SPDXID": "SPDXRef-DOCUMENT",
-  "name": "simple@1.0.0",
-  "documentNamespace": "http://spdx.org/spdxdocs/simple-1.0.0-bf81090e-8bbc-459d-bec9-abeb794e096a",
-  "creationInfo": {
-    "created": "2023-09-01T00:00:00.001Z",
-    "creators": \[lB]
-      "Tool: npm/cli-10.1.0"
-    \[rB]
-  },
-  "documentDescribes": \[lB]
-    "SPDXRef-Package-simple-1.0.0"
-  \[rB],
-  "packages": \[lB]
-    {
-      "name": "simple",
-      "SPDXID": "SPDXRef-Package-simple-1.0.0",
-      "versionInfo": "1.0.0",
-      "packageFileName": "",
-      "description": "simple react app",
-      "primaryPackagePurpose": "LIBRARY",
-      "downloadLocation": "NOASSERTION",
-      "filesAnalyzed": false,
-      "homepage": "NOASSERTION",
-      "licenseDeclared": "MIT",
-      "externalRefs": \[lB]
-        {
-          "referenceCategory": "PACKAGE-MANAGER",
-          "referenceType": "purl",
-          "referenceLocator": "pkg:npm/simple@1.0.0"
-        }
-      \[rB]
-    },
-    {
-      "name": "lodash",
-      "SPDXID": "SPDXRef-Package-lodash-4.17.21",
-      "versionInfo": "4.17.21",
-      "packageFileName": "node_modules/lodash",
-      "description": "Lodash modular utilities.",
-      "downloadLocation": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz",
-      "filesAnalyzed": false,
-      "homepage": "https://lodash.com/",
-      "licenseDeclared": "MIT",
-      "externalRefs": \[lB]
-        {
-          "referenceCategory": "PACKAGE-MANAGER",
-          "referenceType": "purl",
-          "referenceLocator": "pkg:npm/lodash@4.17.21"
-        }
-      \[rB],
-      "checksums": \[lB]
-        {
-          "algorithm": "SHA512",
-          "checksumValue": "bf690311ee7b95e713ba568322e3533f2dd1cb880b189e99d4edef13592b81764daec43e2c54c61d5c558dc5cfb35ecb85b65519e74026ff17675b6f8f916f4a"
-        }
-      \[rB]
-    }
-  \[rB],
-  "relationships": \[lB]
-    {
-      "spdxElementId": "SPDXRef-DOCUMENT",
-      "relatedSpdxElement": "SPDXRef-Package-simple-1.0.0",
-      "relationshipType": "DESCRIBES"
-    },
-    {
-      "spdxElementId": "SPDXRef-Package-simple-1.0.0",
-      "relatedSpdxElement": "SPDXRef-Package-lodash-4.17.21",
-      "relationshipType": "DEPENDS_ON"
-    }
-  \[rB]
-}
-.fi
-.RE
-.SS "Package lock only mode"
-.P
-If package-lock-only is enabled, only the information in the package lock (or shrinkwrap) is loaded. This means that information from the package.json files of your dependencies will not be included in the result set (e.g. description, homepage, engines).
-.SS "Configuration"
-.SS "\fBomit\fR"
-.RS 0
-.IP \(bu 4
-Default: 'dev' if the \fBNODE_ENV\fR environment variable is set to 'production'; otherwise, empty.
-.IP \(bu 4
-Type: "dev", "optional", or "peer" (can be set multiple times)
-.RE 0
-
-.P
-Dependency types to omit from the installation tree on disk.
-.P
-Note that these dependencies \fIare\fR still resolved and added to the \fBpackage-lock.json\fR or \fBnpm-shrinkwrap.json\fR file. They are just not physically installed on disk.
-.P
-If a package type appears in both the \fB--include\fR and \fB--omit\fR lists, then it will be included.
-.P
-If the resulting omit list includes \fB'dev'\fR, then the \fBNODE_ENV\fR environment variable will be set to \fB'production'\fR for all lifecycle scripts.
-.SS "\fBpackage-lock-only\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-If set to true, the current operation will only use the \fBpackage-lock.json\fR, ignoring \fBnode_modules\fR.
-.P
-For \fBupdate\fR this means only the \fBpackage-lock.json\fR will be updated, instead of checking \fBnode_modules\fR and downloading dependencies.
-.P
-For \fBlist\fR this means the output will be based on the tree described by the \fBpackage-lock.json\fR, rather than the contents of \fBnode_modules\fR.
-.SS "\fBsbom-format\fR"
-.RS 0
-.IP \(bu 4
-Default: null
-.IP \(bu 4
-Type: "cyclonedx" or "spdx"
-.RE 0
-
-.P
-SBOM format to use when generating SBOMs.
-.SS "\fBsbom-type\fR"
-.RS 0
-.IP \(bu 4
-Default: "library"
-.IP \(bu 4
-Type: "library", "application", or "framework"
-.RE 0
-
-.P
-The type of package described by the generated SBOM. For SPDX, this is the value for the \fBprimaryPackagePurpose\fR field. For CycloneDX, this is the value for the \fBtype\fR field.
-.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 "package spec"
-.IP \(bu 4
-npm help "dependency selectors"
-.IP \(bu 4
-\fBpackage.json\fR \fI\(la/configuring-npm/package-json\(ra\fR
-.IP \(bu 4
-npm help workspaces
-.RE 0

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

@@ -1,156 +0,0 @@
-.TH "NPM-SEARCH" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-search\fR - Search for packages
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm search <search term> \[lB]<search term> ...\[rB]
-
-aliases: find, s, se
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "Description"
-.P
-Search the registry for packages matching the search terms. \fBnpm search\fR performs a linear, incremental, lexically-ordered search through package metadata for all files in the registry. If your terminal has color support, it will further highlight the matches in the results. This can be disabled with the config item \fBcolor\fR
-.P
-Additionally, using the \fB--searchopts\fR and \fB--searchexclude\fR options paired with more search terms will include and exclude further patterns. The main difference between \fB--searchopts\fR and the standard search terms is that the former does not highlight results in the output and you can use them more fine-grained filtering. Additionally, you can add both of these to your config to change default search filtering behavior.
-.P
-Search also allows targeting of maintainers in search results, by prefixing their npm username with \fB=\fR.
-.P
-If a term starts with \fB/\fR, then it's interpreted as a regular expression and supports standard JavaScript RegExp syntax. In this case search will ignore a trailing \fB/\fR . (Note you must escape or quote many regular expression characters in most shells.)
-.SS "Configuration"
-.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 "\fBcolor\fR"
-.RS 0
-.IP \(bu 4
-Default: true unless the NO_COLOR environ is set to something other than '0'
-.IP \(bu 4
-Type: "always" or Boolean
-.RE 0
-
-.P
-If false, never shows colors. If \fB"always"\fR then always shows colors. If true, then only prints color codes for tty file descriptors.
-.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 "\fBdescription\fR"
-.RS 0
-.IP \(bu 4
-Default: true
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Show the description in \fBnpm search\fR
-.SS "\fBsearchlimit\fR"
-.RS 0
-.IP \(bu 4
-Default: 20
-.IP \(bu 4
-Type: Number
-.RE 0
-
-.P
-Number of items to limit search results to. Will not apply at all to legacy searches.
-.SS "\fBsearchopts\fR"
-.RS 0
-.IP \(bu 4
-Default: ""
-.IP \(bu 4
-Type: String
-.RE 0
-
-.P
-Space-separated options that are always passed to search.
-.SS "\fBsearchexclude\fR"
-.RS 0
-.IP \(bu 4
-Default: ""
-.IP \(bu 4
-Type: String
-.RE 0
-
-.P
-Space-separated options that limit the results from search.
-.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 "\fBprefer-online\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-If true, staleness checks for cached data will be forced, making the CLI look for updates immediately even for fresh package data.
-.SS "\fBprefer-offline\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server. To force full offline mode, use \fB--offline\fR.
-.SS "\fBoffline\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Force offline mode: no network requests will be done during install. To allow the CLI to fill in missing cache data, see \fB--prefer-offline\fR.
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help registry
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help npmrc
-.IP \(bu 4
-npm help view
-.IP \(bu 4
-npm help cache
-.IP \(bu 4
-https://npm.im/npm-registry-fetch
-.RE 0

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

@@ -1,32 +0,0 @@
-.TH "NPM-SHRINKWRAP" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-shrinkwrap\fR - Lock down dependency versions for publication
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm shrinkwrap
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "Description"
-.P
-This command repurposes \fBpackage-lock.json\fR into a publishable \fBnpm-shrinkwrap.json\fR 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\fR files. For a detailed explanation of the design and purpose of package locks in npm, see npm help package-lock-json.
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help install
-.IP \(bu 4
-npm help run
-.IP \(bu 4
-npm help scripts
-.IP \(bu 4
-\fBpackage.json\fR \fI\(la/configuring-npm/package-json\(ra\fR
-.IP \(bu 4
-\fBpackage-lock.json\fR \fI\(la/configuring-npm/package-lock-json\(ra\fR
-.IP \(bu 4
-\fBnpm-shrinkwrap.json\fR \fI\(la/configuring-npm/npm-shrinkwrap-json\(ra\fR
-.IP \(bu 4
-npm help ls
-.RE 0

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

@@ -1,77 +0,0 @@
-.TH "NPM-STAR" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-star\fR - Mark your favorite packages
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm star \[lB]<package-spec>...\[rB]
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "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
-It's a boolean thing. Starring repeatedly has no additional effect.
-.SS "More"
-.P
-There's also these extra commands to help you manage your favorite packages:
-.SS "Unstar"
-.P
-You can also "unstar" a package using npm help unstar
-.P
-"Unstarring" is the same thing, but in reverse.
-.SS "Listing stars"
-.P
-You can see all your starred packages using npm help stars
-.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 "\fBunicode\fR"
-.RS 0
-.IP \(bu 4
-Default: false on windows, true on mac/unix systems with a unicode locale, as defined by the \fBLC_ALL\fR, \fBLC_CTYPE\fR, or \fBLANG\fR environment variables.
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs.
-.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 "package spec"
-.IP \(bu 4
-npm help unstar
-.IP \(bu 4
-npm help stars
-.IP \(bu 4
-npm help view
-.IP \(bu 4
-npm help whoami
-.IP \(bu 4
-npm help adduser
-.RE 0

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

@@ -1,41 +0,0 @@
-.TH "NPM-STARS" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-stars\fR - View packages marked as favorites
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm stars \[lB]<user>\[rB]
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "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.
-.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 star
-.IP \(bu 4
-npm help unstar
-.IP \(bu 4
-npm help view
-.IP \(bu 4
-npm help whoami
-.IP \(bu 4
-npm help adduser
-.RE 0

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

@@ -1,79 +0,0 @@
-.TH "NPM-START" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-start\fR - Start a package
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm start \[lB]-- <args>\[rB]
-.fi
-.RE
-.SS "Description"
-.P
-This runs a predefined command specified in the \fB"start"\fR property of a package's \fB"scripts"\fR object.
-.P
-If the \fB"scripts"\fR object does not define a \fB"start"\fR property, npm will run \fBnode server.js\fR.
-.P
-Note that this is different from the default node behavior of running the file specified in a package's \fB"main"\fR attribute when evoking with \fBnode .\fR
-.P
-As of \fB\[rs]fBnpm@2.0.0\[rs]fR\fR \fI\(lahttps://blog.npmjs.org/post/98131109725/npm-2-0-0\(ra\fR, you can use custom arguments when executing scripts. Refer to npm help run for more details.
-.SS "Example"
-.P
-.RS 2
-.nf
-{
-  "scripts": {
-    "start": "node foo.js"
-  }
-}
-.fi
-.RE
-.P
-.RS 2
-.nf
-npm start
-
-> npm@x.x.x start
-> node foo.js
-
-(foo.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 restart
-.IP \(bu 4
-npm help stop
-.RE 0