-
-
Notifications
You must be signed in to change notification settings - Fork 228
feat: add support for .corepack.env
#642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 7 commits
425709b
4f492c9
dbb2cc4
f53f220
54365fb
ca3cde6
fc05286
ce92d70
5911687
8da557c
3aad295
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -267,6 +267,7 @@ same major line. Should you need to upgrade to a new major, use an explicit | |
| set to `1` to have the URL shown. By default, when Corepack is called | ||
| explicitly (e.g. `corepack pnpm …`), it is set to `0`; when Corepack is called | ||
| implicitly (e.g. `pnpm …`), it is set to `1`. | ||
| The default value cannot be overridden in a `.corepack.env` file. | ||
| When standard input is a TTY and no CI environment is detected, Corepack will | ||
| ask for user input before starting the download. | ||
|
|
||
|
|
@@ -292,6 +293,14 @@ same major line. Should you need to upgrade to a new major, use an explicit | |
| project. This means that it will always use the system-wide package manager | ||
| regardless of what is being specified in the project's `packageManager` field. | ||
|
|
||
| - `COREPACK_ENV_FILE` can be set to `0` to request Corepack to not attempt to | ||
| load `.corepack.env`; it can be set to a path to specify a different env file. | ||
| Only keys that starts with `COREPACK_` will be taken into account, not all | ||
| keys that start with `COREPACK_` will be taken into account ( | ||
| `COREPACK_ENABLE_DOWNLOAD_PROMPT` and `COREPACK_ENV_FILE` are ignored). | ||
|
||
| For Node.js 18.x users, this setting has no effect as that version doesn't | ||
| support parsing of `.env` files. | ||
|
|
||
| - `COREPACK_HOME` can be set in order to define where Corepack should install | ||
| the package managers. By default it is set to `%LOCALAPPDATA%\node\corepack` | ||
| on Windows, and to `$HOME/.cache/node/corepack` everywhere else. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.