Skip to content

feat: support user configuration files - #919

Closed
Aschenbath wants to merge 1 commit into
nodejs:mainfrom
Aschenbath:feat/user-config-510
Closed

Aschenbath wants to merge 1 commit into
nodejs:mainfrom
Aschenbath:feat/user-config-510

Conversation

@Aschenbath

Copy link
Copy Markdown

Load user-wide Corepack defaults from ~/.corepackrc using the same dotenv syntax and COREPACK_* keys as .corepack.env. Explicit environment values take precedence over project settings, then user defaults. COREPACK_CONFIG_FILE selects a different file or disables loading with 0.

Both utility commands and package-manager shims load the user configuration, including the download-prompt setting, before applying their defaults. Documented precedence, supported keys, and error handling; added unit and CLI coverage.

Validation: build, TypeScript, and ESLint pass; user configuration tests pass (18/18). The complete Vitest suite is running with inherited proxy variables cleared to isolate the local proxy fixtures; its result will be added when it completes.

Closes #510

Load user-wide COREPACK_* defaults from ~/.corepackrc or COREPACK_CONFIG_FILE, preserving explicit environment and project configuration precedence. Initialize download-prompt defaults after loading user configuration and document the file format and controls.
@aduh95

aduh95 commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

This account has opened more than 10 PRs in the last 24 hours. This looks like bot activity, and will result in a ban if the behavior continues.

@aduh95 aduh95 closed this Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feature request: support configuration via config file

2 participants