dylang/npm-check

support for proxy config

Open

#106 创建于 2016年3月31日

在 GitHub 查看
 (11 评论) (7 反应) (0 负责人)JavaScript (6,438 star) (278 fork)batch import
help wantedissue is in a dependency

描述

16:23 $ npm-check

autosuggest-highlight      ⛔️  NPM ERR!  Registry error getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
...

both env http_proxy, https_proxy (lower and uppercasE) and npm proxy and https_proxy are setup.

I guess this is because of @sindresorhus 's package-json - see https://github.com/sindresorhus/package-json/blob/master/index.js#L13

贡献者指南

技术栈
javascriptnodejsshell
领域
clideveloper experiencebackend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Node.js basicsnpm proxy configurationunderstanding of HTTP requests
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate how npm check fetches package data. The issue points to the 'package json' package as the cause. Look at the code in index.js (or similar entry point) that calls package json. Consider using a proxy agent like https proxy agent to support proxy settings. Also check if npm registry client is used and configure it for proxy. Test with a proxy server and ensure environment variables and npm config are properly read.