preactjs/wmr

Make npm registry url configurable

Open

#167 创建于 2020年10月20日

在 GitHub 查看
 (4 评论) (3 反应) (0 负责人)JavaScript (4,903 star) (114 fork)batch import
enhancementgood first issuehelp wantedreliability

描述

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.

贡献者指南

技术栈
javascriptnodejs
领域
clideveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Familiarity with Node.jsUnderstanding of npm registryBasic CLI development
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
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.
Make npm registry url configurable · preactjs/wmr#167 | Good First Issue