preactjs/wmr

Make npm registry url configurable

Open

#167 opened on Oct 20, 2020

View on GitHub
 (4 comments) (3 reactions) (0 assignees)JavaScript (4,903 stars) (114 forks)batch import
enhancementgood first issuehelp wantedreliability

Description

Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.

I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in our tests to point to our mocked server.

Contributor guide

Tech stack
javascriptnodejs
Domain
clideveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with Node.jsUnderstanding of npm registryBasic CLI development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue requests a ` registry` CLI flag to specify a custom npm registry URL. Look at the existing CLI argument parsing in WMR, likely in `src/cli.js` or similar, to understand how flags are defined. The npm resolution logic (probably in a plugin) needs to use the custom registry when provided. Tests can be added by spinning up a mock registry server and passing the flag. No linked PRs or comments indicate ongoing work; the issue is open and unassigned.