Feature request: `COREPACK_NPM_REGISTRY ` defaults to `$(npm config get registry)`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
Currently, the default value of COREPACK_NPM_REGISTRY is https://registry.npmjs.org.
My npm registry has been changed to another one, while corepack is still using https://registry.npmjs.org.
Setting up COREPACK_NPM_REGISTRY value to follow $(npm config get registry) (the configed npm registry) is convenient, so that I don't need to concern the registry of corepack
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace where Corepack resolves the default COREPACK_NPM_REGISTRY value and how it can obtain the configured npm registry. Check the existing registry-related behavior and tests before changing it; done means Corepack follows the value from npm config get registry when the environment variable is unset, with tests covering the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100