[BUG] corepack not use COREPACK_NPM_REGISTRY install of tarball

Open Beginner friendly
#792 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
node.js, typescript
Domain
tooling

Research direction

Start at the installVersion entry point and inspect the URL handling around lines 243 and 249, tracing how COREPACK_NPM_REGISTRY is applied during tarball installation. Confirm that the configured registry remains the tarball source when the environment variable is set, and add or run a regression test covering that case.

Written by the indexing model from the issue text.

Description

When the COREPACK_NPM_REGISTRY environment variable is set, the tarball mirror URL is always used instead of the one set in COREPACK_NPM_REGISTRY.

This is likely because the URL in line 243 of installVersion is overwritten with the tarball address, but the replace function in line 249 still replaces it with DEFAULT_NPM_REGISTRY_URL.

Dominant language
TypeScript
Stars
3.8k
Forks
279
Avg merge
1h 47m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/corepack

All issues in nodejs/corepack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.