npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

get-url-proxy

v1.1.2

Published

get-url-proxy will return the applicable proxy to use for a given URL based on NO_PROXY and PROT_PROXY environment variables

Downloads

17

Readme

node-get-url-proxy

get-url-proxy will return the applicable proxy to use for a given URL based on NO_PROXY and {PROTOCOL}_PROXY environment variables.

console.log(process.env.HTTP_PROXY) // "http://proxy:8080/"
console.log(process.env.NO_PROXY); // ".foo.com,192.168.1."

// requires protocol & domain
var getProxy = require('get-url-proxy');
getProxy('http://foo.com/'); // null
noProxy('https://www.google.com/'); // "http://proxy:8080/"

// the cached wrapper will cache the last 100 resources
var cachedProxy = require('get-url-proxy/cached');

// protocol only, without NO_PROXY check
var protocolProxy = require('get-url-proxy/protocol');
protocolProxy('https'): // "http://proxy:8080/"

Search Order

The following search order will be used, generally speaking...

  • NO_PROXY exclusion will return null
  • PROTOCOL_PROXY
  • protocol_proxy
  • ALL_PROXY
  • all_proxy
  • null will be returned with no match.

Web protocols

For web based protocols, additional/similar protocols will be searched as a fallback.

  • HTTP -> [HTTP, HTTPS]
  • HTTPS -> [HTTPS, HTTP]
  • WS -> [WS, WSS, HTTPS, HTTP]
  • WSS -> [WSS, WS, HTTPS, HTTP]
  • SFTP -> [SFTP, SSH]

All other protocols will only search for their own protocol specifically, falling back to ALL_PROXY


NOTE: You may want to use memoization around this module.

WARNING

If you are using a node version prior to Node 8, you should install url-parse as a dependency.