dylang/npm-check

support for proxy config

Open

#106 opened on Mar 31, 2016

View on GitHub
 (11 comments) (7 reactions) (0 assignees)JavaScript (6,438 stars) (278 forks)batch import
help wantedissue is in a dependency

Description

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

Contributor guide

Tech stack
javascriptnodejsshell
Domain
clideveloper experiencebackend
Issue type
bug
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
Node.js basicsnpm proxy configurationunderstanding of HTTP requests
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.