Merge branch 'release-next' into lk/arb-bin

AUTHORS

@@ -821,3 +821,7 @@ linkgoron <Linkgoron@users.noreply.github.com>
 Quentin Barbe <forty@everteam.org>
 dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
 Delapouite <delapouite@gmail.com>
+F. Hinkelmann <franziska.hinkelmann@gmail.com>
+Tierney Cyren <hello@bnb.im>
+Mohamed Akram <mohd-akram@users.noreply.github.com>
+Wassim Chegham <1699357+manekinekko@users.noreply.github.com>

CHANGELOG.md

@@ -1,3 +1,40 @@
+## v8.5.1 (2022-02-17)
+
+### Dependencies
+
+* [`54cda9697`](https://github.com/npm/cli/commit/54cda9697b776fae807966097315c7b836623743)
+  [#4410](https://github.com/npm/cli/pull/4410)
+  fix(arborist): do not audit in offline mode
+  ([@mohd-akram](https://github.com/mohd-akram))
+* [`fb13bdaf1`](https://github.com/npm/cli/commit/fb13bdaf12dde3ef5685a77354e51a9cfa579879)
+  [#4403](https://github.com/npm/cli/pull/4403)
+  deps: `@npmcli/ci-detect@2.0.0`
+* [`702801002`](https://github.com/npm/cli/commit/702801002e99bf02dd4d6d1e447a5ab332d56c79)
+  [#4415](https://github.com/npm/cli/pull/4415)
+  deps: `make-fetch-happen@10.0.3`
+* [`88bab3540`](https://github.com/npm/cli/commit/88bab354097023c96c49e78d7ee54159f495bf73)
+  [#4416](https://github.com/npm/cli/pull/4416)
+  deps: `gauge@4.0.1`
+
+### Documentation
+
+* [`20378c67c`](https://github.com/npm/cli/commit/20378c67cd533db514dd2aec7828c6d119e9d6c7)
+  [#4423](https://github.com/npm/cli/pull/4423)
+  docs: update documentation for ping
+  ([@fhinkel](https://github.com/fhinkel))
+* [`408d2fc15`](https://github.com/npm/cli/commit/408d2fc150185ef66125f7d6bdb1c25edb71bba3)
+  [#4426](https://github.com/npm/cli/pull/4426)
+  docs: update workspaces guide for consistency
+  ([@bnb](https://github.com/bnb))
+* [`9275856eb`](https://github.com/npm/cli/commit/9275856eb75e7c394a3c7617c2b495aba35ee2de)
+  [#4424](https://github.com/npm/cli/pull/4424)
+  docs: update usage example for npm pkg
+  ([@manekinekko](https://github.com/manekinekko))
+* [`20c83fae7`](https://github.com/npm/cli/commit/20c83fae76ff4a051e4f6542a328f1c00cf071bb)
+  [#4428](https://github.com/npm/cli/pull/4428)
+  docs: update docs for npm install <folder>
+  ([@manekinekko](https://github.com/manekinekko))
+
 ## v8.5.0 (2022-02-10)
 
 ### Features

docs/content/commands/npm-init.md

@@ -38,6 +38,15 @@ strictly additive, so it will keep any fields and values that were already
 set. You can also use `-y`/`--yes` to skip the questionnaire altogether. If
 you pass `--scope`, it will create a scoped package.
 
+*Note:* if a user already has the `create-<initializer>` package
+globally installed, that will be what `npm init` uses.  If you want npm
+to use the latest version, or another specific version you must specify
+it:
+
+* `npm init foo@latest` # fetches and runs the latest `create-foo` from
+    the registry
+* `npm init foo@1.2.3` #  runs `create-foo@1.2.3` specifically
+
 #### Forwarding additional options
 
 Any additional options will be passed directly to the command, so `npm init

docs/content/commands/npm-install.md

@@ -78,11 +78,20 @@ into a tarball (b).
 
 * `npm install <folder>`:
 
-    Install the package in the directory as a symlink in the current
-    project.  Its dependencies will be installed before it's linked. If
-    `<folder>` sits inside the root of your project, its dependencies may
+    If `<folder>` sits inside the root of your project, its dependencies will be installed and may
     be hoisted to the top-level `node_modules` as they would for other
-    types of dependencies.
+    types of dependencies. If `<folder>` sits outside the root of your project,
+    *npm will not install the package dependencies* in the directory `<folder>`, 
+    but it will create a symlink to `<folder>`.
+
+    > NOTE: If you want to install the content of a directory like a package from the registry instead of creating a link, you would need to use [`npm pack`](/commands/npm-pack) while in the `<folder>` directory, and then install the resulting tarball instead of the `<folder>` using `npm install <tarball file>`
+
+    Example:
+
+    ```bash
+    npm install ../../other-package
+    npm install ./sub-package
+    ```
 
 * `npm install <tarball file>`:
 

docs/content/using-npm/scripts.md

@@ -344,6 +344,11 @@ file.
   preinstall or install script. If you are doing this, please consider if
   there is another option. The only valid use of `install` or `preinstall`
   scripts is for compilation which must be done on the target architecture.
+* Scripts are run from the root of the package folder, regardless of what the
+  current working directory is when `npm` is invoked. If you want your
+  script to use different behavior based on what subdirectory you're in, you
+  can use the `INIT_CWD` environment variable, which holds the full path you
+  were in when you ran `npm run`.
 
 ### See Also
 

node_modules/.gitignore

@@ -69,6 +69,7 @@ readme*
 /acorn-walk
 /ajv
 /ansi-colors
+/ansi-regex
 /anymatch
 /append-transform
 /arg
@@ -379,6 +380,7 @@ readme*
 /state-toggle
 /string.prototype.trimend
 /string.prototype.trimstart
+/strip-ansi
 /strip-json-comments
 /style-to-object
 /symbol-tree