support for proxy config
See original GitHub issue16: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
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Use a proxy server in Windows - Microsoft Support
To set up a proxy server connection manually · Select the Start button, then select Settings > Network & internet > Proxy. ·...
Read more >Change proxy settings on Mac - Apple Support
Learn how to enter proxy server settings. To change these settings, choose Apple menu > System Settings, click Network in the sidebar, click...
Read more >Proxy Configuration
Internet Explorer, Firefox, and Chrome support manual proxy configuration. Users can specify the proxy server and port for each protocol.
Read more >Configuring proxy support in Operator Lifecycle Manager
If a global proxy is configured on the OpenShift Container Platform cluster, Operator Lifecycle Manager (OLM) automatically configures Operators that it manages ...
Read more >How to Set Up a Proxy Server on Your PC, Mac, or Web Browser
Before setting up a proxy server, you need to check the proxy settings on your computer. The information in proxy settings can help...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also behind a proxy and use
npm-check
frequently. My temporary workaround is to manually editnpm-check/node_modules/package-json/index.js
:Thanks @robmcguinness for the fix with caw. I have forked the original package-json, and made the changes you suggested in the fork. Anyone requiring an easier fix, see the “Usage” section in the readme