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.
support for proxy config · dylang/npm-check#106 | Good First Issue