npm / npm/rfcs

[RRFC] --registry=default or --default-registry support

Open
#379 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
777
Forks
267
PR merge metrics
No merged PRs in 30d

Description

Motivation

At times for most of the CLI commands that provide support for --registry we would override the proxy with providing the default npm registry URL, rather this would be simpler if we were to have --registry=default option that would set it or use the default npm reg.

Example
npm install --registry=https://registry.npmjs.org/ 

# isn't of ^ we can use 

npm install --registry=default

# or 

npm install --default-registry
npm config set registry https://registry.npmjs.org/

# isn't of ^ we can use 

npm config set registry default
How
Current Behaviour

There is not options other than specifying the URL

Desired Behaviour

Support for --registry=default

References
  • n/a

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.

Research direction

Start by reviewing the requested behavior for npm CLI commands that accept --registry and the npm config registry setting. Compare the proposed default value and --default-registry form with current command and configuration behavior. Done means the chosen syntax consistently selects the default npm registry without requiring its URL.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.