@mixedbread/sdk 0.50.0 → 0.50.1

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

@@ -1,291 +0,0 @@
-.TH "NPM-DEDUPE" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-dedupe\fR - Reduce duplication in the package tree
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm dedupe
-
-alias: ddp
-.fi
-.RE
-.SS "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, \fBnpm dedupe\fR 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
-In some cases, you may have a dependency graph like this:
-.P
-.RS 2
-.nf
-a
-+-- b <-- depends on c@1.0.x
-+-- c@1.0.3
-`-- d <-- depends on c@1.x
-    `-- c@1.9.9
-.fi
-.RE
-.P
-During the installation process, the \fBc@1.0.3\fR dependency for \fBb\fR was placed in the root of the tree. Though \fBd\fR's dependency on \fBc@1.x\fR could have been satisfied by \fBc@1.0.3\fR, the newer \fBc@1.9.0\fR dependency was used, because npm favors updates by default, even when doing so causes duplication.
-.P
-Running \fBnpm dedupe\fR will cause npm to note the duplication and re-evaluate, deleting the nested \fBc\fR module, because the one in the root is sufficient.
-.P
-To prefer deduplication over novelty during the installation process, run \fBnpm install --prefer-dedupe\fR or \fBnpm config set prefer-dedupe true\fR.
-.P
-Arguments are ignored. Dedupe always acts on the entire tree.
-.P
-Note that this operation transforms the dependency tree, but will never result in new modules being installed.
-.P
-Using \fBnpm find-dupes\fR will run the command in \fB--dry-run\fR mode.
-.P
-Note: \fBnpm dedupe\fR will never update the semver values of direct dependencies in your project \fBpackage.json\fR, if you want to update values in \fBpackage.json\fR you can run: \fBnpm update --save\fR instead.
-.SS "Configuration"
-.SS "\fBinstall-strategy\fR"
-.RS 0
-.IP \(bu 4
-Default: "hoisted"
-.IP \(bu 4
-Type: "hoisted", "nested", "shallow", or "linked"
-.RE 0
-
-.P
-Sets the strategy for installing packages in node_modules. hoisted (default): Install non-duplicated in top-level, and duplicated as necessary within directory structure. nested: (formerly --legacy-bundling) install in place, no hoisting. shallow (formerly --global-style) only install direct deps at top-level. linked: (experimental) install in node_modules/.store, link in place, unhoisted.
-.SS "\fBlegacy-bundling\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.IP \(bu 4
-DEPRECATED: This option has been deprecated in favor of \fB--install-strategy=nested\fR
-.RE 0
-
-.P
-Instead of hoisting package installs in \fBnode_modules\fR, install packages in the same manner that they are depended on. This may cause very deep directory structures and duplicate package installs as there is no de-duplicating. Sets \fB--install-strategy=nested\fR.
-.SS "\fBglobal-style\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.IP \(bu 4
-DEPRECATED: This option has been deprecated in favor of \fB--install-strategy=shallow\fR
-.RE 0
-
-.P
-Only install direct dependencies in the top level \fBnode_modules\fR, but hoist on deeper dependencies. Sets \fB--install-strategy=shallow\fR.
-.SS "\fBstrict-peer-deps\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-If set to \fBtrue\fR, and \fB--legacy-peer-deps\fR is not set, then \fIany\fR conflicting \fBpeerDependencies\fR will be treated as an install failure, even if npm could reasonably guess the appropriate resolution based on non-peer dependency relationships.
-.P
-By default, conflicting \fBpeerDependencies\fR deep in the dependency graph will be resolved using the nearest non-peer dependency specification, even if doing so will result in some packages receiving a peer dependency outside the range set in their package's \fBpeerDependencies\fR object.
-.P
-When such an override is performed, a warning is printed, explaining the conflict and the packages involved. If \fB--strict-peer-deps\fR is set, then this warning is treated as a failure.
-.SS "\fBpackage-lock\fR"
-.RS 0
-.IP \(bu 4
-Default: true
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-If set to false, then ignore \fBpackage-lock.json\fR files when installing. This will also prevent \fIwriting\fR \fBpackage-lock.json\fR if \fBsave\fR is true.
-.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 "\fBinclude\fR"
-.RS 0
-.IP \(bu 4
-Default:
-.IP \(bu 4
-Type: "prod", "dev", "optional", or "peer" (can be set multiple times)
-.RE 0
-
-.P
-Option that allows for defining which types of dependencies to install.
-.P
-This is the inverse of \fB--omit=<type>\fR.
-.P
-Dependency types specified in \fB--include\fR will not be omitted, regardless of the order in which omit/include are specified on the command-line.
-.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 "\fBaudit\fR"
-.RS 0
-.IP \(bu 4
-Default: true
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-When "true" submit audit reports alongside the current npm command to the default registry and all registries configured for scopes. See the documentation for npm help audit for details on what is submitted.
-.SS "\fBbin-links\fR"
-.RS 0
-.IP \(bu 4
-Default: true
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Tells npm to create symlinks (or \fB.cmd\fR shims on Windows) for package executables.
-.P
-Set to false to have it not do this. This can be used to work around the fact that some file systems don't support symlinks, even on ostensibly Unix systems.
-.SS "\fBfund\fR"
-.RS 0
-.IP \(bu 4
-Default: true
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-When "true" displays the message at the end of each \fBnpm install\fR acknowledging the number of dependencies looking for funding. See npm help fund for details.
-.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 "\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 find-dupes
-.IP \(bu 4
-npm help ls
-.IP \(bu 4
-npm help update
-.IP \(bu 4
-npm help install
-.RE 0

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

@@ -1,86 +0,0 @@
-.TH "NPM-DEPRECATE" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-deprecate\fR - Deprecate a version of a package
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm deprecate <package-spec> <message>
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "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 \fBversion ranges\fR \fI\(lahttps://semver.npmjs.com/\(ra\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
-SemVer ranges passed to this command are interpreted such that they \fIdo\fR include prerelease versions. For example:
-.P
-.RS 2
-.nf
-npm deprecate my-thing@1.x "1.x is no longer supported"
-.fi
-.RE
-.P
-In this case, a version \fBmy-thing@1.0.0-beta.0\fR will also be deprecated.
-.P
-You must be the package owner to deprecate something. See the \fBowner\fR and \fBadduser\fR help topics.
-.P
-To un-deprecate a package, specify an empty string (\fB""\fR) for the \fBmessage\fR argument. Note that you must use double quotes with no space between them to format an empty string.
-.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 "package spec"
-.IP \(bu 4
-npm help publish
-.IP \(bu 4
-npm help registry
-.IP \(bu 4
-npm help owner
-.IP \(bu 4
-npm help adduser
-.RE 0

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

@@ -1,310 +0,0 @@
-.TH "NPM-DIFF" "1" "October 2025" "NPM@11.6.2" ""
-.SH "NAME"
-\fBnpm-diff\fR - The registry diff command
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm diff \[lB]...<paths>\[rB]
-.fi
-.RE
-.SS "Description"
-.P
-Similar to its \fBgit diff\fR counterpart, this command will print diff patches of files for packages published to the npm registry.
-.RS 0
-.IP \(bu 4
-\fBnpm diff --diff=<spec-a> --diff=<spec-b>\fR
-.P
-Compares two package versions using their registry specifiers, e.g: \fBnpm diff --diff=pkg@1.0.0 --diff=pkg@^2.0.0\fR. It's also possible to compare across forks of any package, e.g: \fBnpm diff --diff=pkg@1.0.0 --diff=pkg-fork@1.0.0\fR.
-.P
-Any valid spec can be used, so that it's also possible to compare directories or git repositories, e.g: \fBnpm diff --diff=pkg@latest --diff=./packages/pkg\fR
-.P
-Here's an example comparing two different versions of a package named \fBabbrev\fR from the registry:
-.P
-.RS 2
-.nf
-npm diff --diff=abbrev@1.1.0 --diff=abbrev@1.1.1
-.fi
-.RE
-.P
-On success, output looks like:
-.P
-.RS 2
-.nf
-diff --git a/package.json b/package.json
-index v1.1.0..v1.1.1 100644
---- a/package.json
-+++ b/package.json
-@@ -1,6 +1,6 @@
- {
-   "name": "abbrev",
--  "version": "1.1.0",
-+  "version": "1.1.1",
-   "description": "Like ruby's abbrev module, but in js",
-   "author": "Isaac Z. Schlueter <i@izs.me>",
-   "main": "abbrev.js",
-.fi
-.RE
-.P
-Given the flexible nature of npm specs, you can also target local directories or git repos just like when using \fBnpm install\fR:
-.P
-.RS 2
-.nf
-npm diff --diff=https://github.com/npm/libnpmdiff --diff=./local-path
-.fi
-.RE
-.P
-In the example above we can compare the contents from the package installed from the git repo at \fBgithub.com/npm/libnpmdiff\fR with the contents of the \fB./local-path\fR that contains a valid package, such as a modified copy of the original.
-.IP \(bu 4
-\fBnpm diff\fR (in a package directory, no arguments):
-.P
-If the package is published to the registry, \fBnpm diff\fR will fetch the tarball version tagged as \fBlatest\fR (this value can be configured using the \fBtag\fR option) and proceed to compare the contents of files present in that tarball, with the current files in your local file system.
-.P
-This workflow provides a handy way for package authors to see what package-tracked files have been changed in comparison with the latest published version of that package.
-.IP \(bu 4
-\fBnpm diff --diff=<pkg-name>\fR (in a package directory):
-.P
-When using a single package name (with no version or tag specifier) as an argument, \fBnpm diff\fR will work in a similar way to \fB\[rs]fBnpm-outdated\[rs]fR\fR \fI\(lanpm-outdated\(ra\fR and reach for the registry to figure out what current published version of the package named \fB<pkg-name>\fR will satisfy its dependent declared semver-range. Once that specific version is known \fBnpm diff\fR will print diff patches comparing the current version of \fB<pkg-name>\fR found in the local file system with that specific version returned by the registry.
-.P
-Given a package named \fBabbrev\fR that is currently installed:
-.P
-.RS 2
-.nf
-npm diff --diff=abbrev
-.fi
-.RE
-.P
-That will request from the registry its most up to date version and will print a diff output comparing the currently installed version to this newer one if the version numbers are not the same.
-.IP \(bu 4
-\fBnpm diff --diff=<spec-a>\fR (in a package directory):
-.P
-Similar to using only a single package name, it's also possible to declare a full registry specifier version if you wish to compare the local version of an installed package with the specific version/tag/semver-range provided in \fB<spec-a>\fR.
-.P
-An example: assuming \fBpkg@1.0.0\fR is installed in the current \fBnode_modules\fR folder, running:
-.P
-.RS 2
-.nf
-npm diff --diff=pkg@2.0.0
-.fi
-.RE
-.P
-It will effectively be an alias to \fBnpm diff --diff=pkg@1.0.0 --diff=pkg@2.0.0\fR.
-.IP \(bu 4
-\fBnpm diff --diff=<semver-a> \[lB]--diff=<semver-b>\[rB]\fR (in a package directory):
-.P
-Using \fBnpm diff\fR along with semver-valid version numbers is a shorthand to compare different versions of the current package.
-.P
-It needs to be run from a package directory, such that for a package named \fBpkg\fR running \fBnpm diff --diff=1.0.0 --diff=1.0.1\fR is the same as running \fBnpm diff --diff=pkg@1.0.0 --diff=pkg@1.0.1\fR.
-.P
-If only a single argument \fB<version-a>\fR is provided, then the current local file system is going to be compared against that version.
-.P
-Here's an example comparing two specific versions (published to the configured registry) of the current project directory:
-.P
-.RS 2
-.nf
-npm diff --diff=1.0.0 --diff=1.1.0
-.fi
-.RE
-.RE 0
-
-.P
-Note that tag names are not valid \fB--diff\fR argument values, if you wish to compare to a published tag, you must use the \fBpkg@tagname\fR syntax.
-.SS "Filtering files"
-.P
-It's possible to also specify positional arguments using file names or globs pattern matching in order to limit the result of diff patches to only a subset of files for a given package, e.g:
-.P
-.RS 2
-.nf
-npm diff --diff=pkg@2 ./lib/ CHANGELOG.md
-.fi
-.RE
-.P
-In the example above the diff output is only going to print contents of files located within the folder \fB./lib/\fR and changed lines of code within the \fBCHANGELOG.md\fR file.
-.SS "Configuration"
-.SS "\fBdiff\fR"
-.RS 0
-.IP \(bu 4
-Default:
-.IP \(bu 4
-Type: String (can be set multiple times)
-.RE 0
-
-.P
-Define arguments to compare in \fBnpm diff\fR.
-.SS "\fBdiff-name-only\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Prints only filenames when using \fBnpm diff\fR.
-.SS "\fBdiff-unified\fR"
-.RS 0
-.IP \(bu 4
-Default: 3
-.IP \(bu 4
-Type: Number
-.RE 0
-
-.P
-The number of lines of context to print in \fBnpm diff\fR.
-.SS "\fBdiff-ignore-all-space\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Ignore whitespace when comparing lines in \fBnpm diff\fR.
-.SS "\fBdiff-no-prefix\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Do not show any source or destination prefix in \fBnpm diff\fR output.
-.P
-Note: this causes \fBnpm diff\fR to ignore the \fB--diff-src-prefix\fR and \fB--diff-dst-prefix\fR configs.
-.SS "\fBdiff-src-prefix\fR"
-.RS 0
-.IP \(bu 4
-Default: "a/"
-.IP \(bu 4
-Type: String
-.RE 0
-
-.P
-Source prefix to be used in \fBnpm diff\fR output.
-.SS "\fBdiff-dst-prefix\fR"
-.RS 0
-.IP \(bu 4
-Default: "b/"
-.IP \(bu 4
-Type: String
-.RE 0
-
-.P
-Destination prefix to be used in \fBnpm diff\fR output.
-.SS "\fBdiff-text\fR"
-.RS 0
-.IP \(bu 4
-Default: false
-.IP \(bu 4
-Type: Boolean
-.RE 0
-
-.P
-Treat all files as text in \fBnpm diff\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 "\fBtag\fR"
-.RS 0
-.IP \(bu 4
-Default: "latest"
-.IP \(bu 4
-Type: String
-.RE 0
-
-.P
-If you ask npm to install a package and don't tell it a specific version, then it will install the specified tag.
-.P
-It is the tag added to the package@version specified in the \fBnpm
-dist-tag add\fR command, if no explicit tag is given.
-.P
-When used by the \fBnpm diff\fR command, this is the tag used to fetch the tarball that will be compared with the local files by default.
-.P
-If used in the \fBnpm publish\fR command, this is the tag that will be added to the package submitted to the registry.
-.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.
-.SH "SEE ALSO"
-.RS 0
-.IP \(bu 4
-npm help outdated
-.IP \(bu 4
-npm help install
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help registry
-.RE 0