poor integration with npm authentication
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
Please don't drop NPM authentication to registries for corepack install yarn.
We shouldn't have to duplicate authentication in the COREPACK_NPM_TOKEN, COREPACK_NPM_USERNAME, and/or COREPACK_NPM_PASSWORD environment variables, when NPM is already setup properly to connect to registries.
corepack and yarn delegate many functions to NPM. They should wrap, not break, NPM functionality.
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
Start at the corepack install yarn command entry point and trace how registry authentication is obtained when npm is already configured. Compare that path with the COREPACK_NPM_TOKEN, COREPACK_NPM_USERNAME, and COREPACK_NPM_PASSWORD variables; done means existing npm registry authentication works without duplicating credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100