diff options
Diffstat (limited to 'tap-snapshots/test/lib/utils/config/definitions.js.test.cjs')
-rw-r--r-- | tap-snapshots/test/lib/utils/config/definitions.js.test.cjs | 32 |
1 files changed, 5 insertions, 27 deletions
diff --git a/tap-snapshots/test/lib/utils/config/definitions.js.test.cjs b/tap-snapshots/test/lib/utils/config/definitions.js.test.cjs index fcfec5941..9d5fe79af 100644 --- a/tap-snapshots/test/lib/utils/config/definitions.js.test.cjs +++ b/tap-snapshots/test/lib/utils/config/definitions.js.test.cjs @@ -63,7 +63,6 @@ Array [ "ignore-scripts", "include", "include-staged", - "include-workspace-root", "init-author-email", "init-author-name", "init-author-url", @@ -832,19 +831,6 @@ Allow installing "staged" published packages, as defined by [npm RFC PR This is experimental, and not implemented by the npm public registry. ` -exports[`test/lib/utils/config/definitions.js TAP > config description for include-workspace-root 1`] = ` -#### \`include-workspace-root\` - -* Default: false -* Type: Boolean - -Include the workspace root when workspaces are enabled for a command. - -When false, specifying individual workspaces via the \`workspace\` config, or -all workspaces via the \`workspaces\` flag, will cause npm to operate only on -the specified workspaces, and not on the root project. -` - exports[`test/lib/utils/config/definitions.js TAP > config description for init-author-email 1`] = ` #### \`init-author-email\` @@ -1853,8 +1839,8 @@ Valid values for the \`workspace\` config are either: * Workspace names * Path to a workspace directory -* Path to a parent workspace directory (will result in selecting all - workspaces within that folder) +* Path to a parent workspace directory (will result to selecting all of the + nested workspaces) When set for the \`npm init\` 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 @@ -1866,20 +1852,12 @@ This value is not exported to the environment for child processes. exports[`test/lib/utils/config/definitions.js TAP > config description for workspaces 1`] = ` #### \`workspaces\` -* Default: null -* Type: null or Boolean +* Default: false +* Type: Boolean -Set to true to run the command in the context of **all** configured +Enable running a command in the context of **all** the configured workspaces. -Explicitly setting this to false will cause commands like \`install\` to -ignore workspaces altogether. When not set explicitly: - -- Commands that operate on the \`node_modules\` tree (install, update, etc.) -will link workspaces into the \`node_modules\` folder. - Commands that do -other things (test, exec, publish, etc.) will operate on the root project, -_unless_ one or more workspaces are specified in the \`workspace\` config. - This value is not exported to the environment for child processes. ` |