@@ -328,8 +328,6 @@ same major line. Should you need to upgrade to a new major, use an explicit
|
328 | 328 | Only keys that start with `COREPACK_` and are not in the exception list |
329 | 329 | (`COREPACK_ENABLE_DOWNLOAD_PROMPT` and `COREPACK_ENV_FILE` are ignored) |
330 | 330 | will be taken into account. |
331 | | - For Node.js 18.x users, this setting has no effect as that version doesn't |
332 | | - support parsing of `.env` files. |
333 | 331 | |
334 | 332 | - `COREPACK_HOME` can be set in order to define where Corepack should install |
335 | 333 | the package managers. By default it is set to `%LOCALAPPDATA%\node\corepack` |
@@ -352,7 +350,7 @@ same major line. Should you need to upgrade to a new major, use an explicit
|
352 | 350 | empty password, explicitly set `COREPACK_NPM_PASSWORD` to an empty string. |
353 | 351 | |
354 | 352 | - `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` are supported through |
355 | | -[`proxy-from-env`](https://github.com/Rob--W/proxy-from-env). |
| 353 | +[`NODE_USE_ENV_PROXY=1`](https://nodejs.org/api/cli.html#node_use_env_proxy1). |
356 | 354 | |
357 | 355 | - `COREPACK_INTEGRITY_KEYS` can be set to an empty string or `0` to |
358 | 356 | instruct Corepack to skip integrity checks, or to a JSON string containing |
|