Skip to content

Commit 8fdabcb

Browse files
npm-robotrichardlau
authored andcommittedOct 18, 2021
deps: upgrade npm to 8.1.0
PR-URL: #40463 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
1 parent bc86084 commit 8fdabcb

File tree

180 files changed

+3239
-2539
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

180 files changed

+3239
-2539
lines changed
 

‎deps/npm/README.md

+5-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,11 @@
44

55
### Requirements
66

7-
* [**Node.js** `v10`](https://nodejs.org/en/download/) or higher must be installed to run this program
7+
One of the following versions of [Node.js](https://nodejs.org/en/download/) must be installed to run **`npm`**:
8+
9+
* `12.x.x` >= `12.13.0`
10+
* `14.x.x` >= `14.15.0`
11+
* `16.0.0` or higher
812

913
### Installation
1014

‎deps/npm/docs/content/commands/npm-audit.md

+27-5
Original file line numberDiff line numberDiff line change
@@ -313,8 +313,8 @@ Valid values for the `workspace` config are either:
313313

314314
* Workspace names
315315
* Path to a workspace directory
316-
* Path to a parent workspace directory (will result to selecting all of the
317-
nested workspaces)
316+
* Path to a parent workspace directory (will result in selecting all
317+
workspaces within that folder)
318318

319319
When set for the `npm init` command, this may be set to the folder of a
320320
workspace which does not yet exist, to create the folder and set it up as a
@@ -327,17 +327,39 @@ This value is not exported to the environment for child processes.
327327

328328
#### `workspaces`
329329

330-
* Default: false
331-
* Type: Boolean
330+
* Default: null
331+
* Type: null or Boolean
332332

333-
Enable running a command in the context of **all** the configured
333+
Set to true to run the command in the context of **all** configured
334334
workspaces.
335335

336+
Explicitly setting this to false will cause commands like `install` to
337+
ignore workspaces altogether. When not set explicitly:
338+
339+
- Commands that operate on the `node_modules` tree (install, update, etc.)
340+
will link workspaces into the `node_modules` folder. - Commands that do
341+
other things (test, exec, publish, etc.) will operate on the root project,
342+
_unless_ one or more workspaces are specified in the `workspace` config.
343+
336344
This value is not exported to the environment for child processes.
337345

338346
<!-- automatically generated, do not edit manually -->
339347
<!-- see lib/utils/config/definitions.js -->
340348

349+
#### `include-workspace-root`
350+
351+
* Default: false
352+
* Type: Boolean
353+
354+
Include the workspace root when workspaces are enabled for a command.
355+
356+
When false, specifying individual workspaces via the `workspace` config, or
357+
all workspaces via the `workspaces` flag, will cause npm to operate only on
358+
the specified workspaces, and not on the root project.
359+
360+
<!-- automatically generated, do not edit manually -->
361+
<!-- see lib/utils/config/definitions.js -->
362+
341363
<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
342364

343365
### See Also

0 commit comments

Comments
 (0)