deps: update corepack to 0.18.0

PR-URL: #48091 Backport-PR-URL: #47337 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
nodejs · Aug 24, 2023 · bbe47a2 · bbe47a2
1 parent 78cf116
commit bbe47a2
Show file tree

Hide file tree

Showing 11 changed files with 39,915 additions and 45,027 deletions.
diff --git a/deps/corepack/CHANGELOG.md b/deps/corepack/CHANGELOG.md
@@ -1,5 +1,26 @@
 # Changelog
 
+## [0.18.0](https://github.com/nodejs/corepack/compare/v0.17.2...v0.18.0) (2023-05-19)
+
+
+### ⚠ BREAKING CHANGES
+
+* remove support for Node.js 14.x
+
+### Features
+
+* update package manager versions ([#256](https://github.com/nodejs/corepack/issues/256)) ([7b61ff6](https://github.com/nodejs/corepack/commit/7b61ff6bc797ec4ed50c2ba1e1f1689264cbf4fc))
+
+
+### Bug Fixes
+
+* **doc:** add a note about troubleshooting network errors ([#259](https://github.com/nodejs/corepack/issues/259)) ([aa3cbdb](https://github.com/nodejs/corepack/commit/aa3cbdb54fb21b8e0adde96dc781cdf750932843))
+
+
+### Miscellaneous Chores
+
+* update supported Node.js versions ([#258](https://github.com/nodejs/corepack/issues/258)) ([74f679d](https://github.com/nodejs/corepack/commit/74f679d8a72cc10a3720fc679b95e9bd086d95be))
+
 ## [0.17.2](https://github.com/nodejs/corepack/compare/v0.17.1...v0.17.2) (2023-04-07)
 
 

diff --git a/deps/corepack/README.md b/deps/corepack/README.md
@@ -2,26 +2,20 @@
 
 Corepack is a zero-runtime-dependency Node.js script that acts as a bridge
 between Node.js projects and the package managers they are intended to be used
-with during development. In practical terms, **Corepack will let you use Yarn
-and pnpm without having to install them** - just like what currently happens
-with npm, which is shipped by Node.js by default.
-
-**Important:** At the moment, Corepack only covers Yarn and pnpm. Given that we
-have little control on the npm project, we prefer to focus on the Yarn and pnpm
-use cases. As a result, Corepack doesn't have any effect at all on the way you
-use npm.
+with during development. In practical terms, **Corepack lets you use Yarn, npm,
+and pnpm without having to install them**.
 
 ## How to Install
 
 ### Default Installs
 
-Corepack is distributed by default with Node.js 14.19.0 and 16.9.0, but is
-opt-in for the time being. Run `corepack enable` to install the required shims.
+Corepack is [distributed by default with all recent Node.js versions](https://nodejs.org/api/corepack.html).
+Run `corepack enable` to install the required Yarn and pnpm binaries on your path.
 
 ### Manual Installs
 
 <details>
-<summary>Click here to see how to install Corepack using npm</summary>
+<summary>Install Corepack using npm</summary>
 
 First uninstall your global Yarn and pnpm binaries (just leave npm). In general,
 you'd do this by running the following command:
@@ -45,6 +39,12 @@ is distributed along with Node.js itself.
 
 </details>
 
+<details><summary>Install Corepack from source</summary>
+
+See [`CONTRIBUTING.md`](./CONTRIBUTING.md).
+
+</details>
+
 ## Usage
 
 ### When Building Packages
@@ -131,12 +131,37 @@ on a project where the `packageManager` field references `pnpm`).
 | --------------------- | --------------------------------------- |
 | `--install-directory` | Add the shims to the specified location |
 
-This command will detect where Node.js is installed and will create shims next
+This command will detect where Corepack is installed and will create shims next
 to it for each of the specified package managers (or all of them if the command
 is called without parameters). Note that the npm shims will not be installed
 unless explicitly requested, as npm is currently distributed with Node.js
 through other means.
 
+If the file system where the `corepack` binary is located is read-only, this
+command will fail. A workaround is to add the binaries as alias in your
+shell configuration file (e.g. in `~/.bash_aliases`):
+
+```sh
+alias yarn="corepack yarn"
+alias yarnpkg="corepack yarnpkg"
+alias pnpm="corepack pnpm"
+alias pnpx="corepack pnpx"
+alias npm="corepack npm"
+alias npx="corepack npx"
+```
+
+On Windows PowerShell, you can add functions using the `$PROFILE` automatic
+variable:
+
+```powershell
+echo "function yarn { corepack yarn `$args }" >> $PROFILE
+echo "function yarnpkg { corepack yarnpkg `$args }" >> $PROFILE
+echo "function pnpm { corepack pnpm `$args }" >> $PROFILE
+echo "function pnpx { corepack pnpx `$args }" >> $PROFILE
+echo "function npm { corepack npm `$args }" >> $PROFILE
+echo "function npx { corepack npx `$args }" >> $PROFILE
+```
+
 ### `corepack disable [... name]`
 
 | Option                | Description                                |
@@ -217,6 +242,16 @@ network interaction.
 - `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` are supported through
   [`node-proxy-agent`](https://github.com/TooTallNate/node-proxy-agent).
 
+## Troubleshooting
+
+### Networking
+
+There are a wide variety of networking issues that can occur while running `corepack` commands. Things to check:
+
+- Make sure your network connection is active.
+- Make sure the host for your request can be resolved by your DNS; try using `curl [URL]` from your shell.
+- Check your proxy settings (see [Environment Variables](#environment-variables)).
+
 ## Contributing
 
 See [`CONTRIBUTING.md`](./CONTRIBUTING.md).