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

proxy-agent-patch

v0.0.4

Published

Monkey patch agent of http and https methods to use an http-proxy

Downloads

9

Readme

Proxy Agent Patch Build Status

Monkey patches the http and https global-agents to use a configured proxy.

Installation

npm install proxy-agent-patch

Usage

Include this before your code or any packages would use nodes http or https

require('proxy-agent-patch')();

If no options are passed proxy-agent-patch will try to infer the proxy settings for http and https from process.env.http_proxy, process.env.https_proxy or process.env.HTTP_PROXY, process.env.HTTPS_PROXY. process.env.no_proxy and process.env.NO_PROXY are also respected;

You can also pass the settings explicitly:

require('proxy-agent-patch')({
  httpProxy: 'http://proxy.com:8080',
  httpsProxy: 'https://proxy.com:8080',
  noProxy: 'localhost, 127.0.0.0'
});

You can also specify an http-proxy for https-connections.

Testing

You can run the tests with

npm test

Note that at the moment tests try to connect to real urls, when testing the no_proxy-setting. This is far from ideal as it will fail if you are behind a proxy as you probably are when trying out this package. It works on Travis for now and will be fixed eventually.

Release History

  • 0.0.x Development Version. Do not use
  • 0.0.1 Initial release version
  • 0.0.2 Refactoring of patching
  • 0.0.3 Add no_proxy-option
  • 0.0.4 Differentiate no_proxy-settings at port level, allow subdomain wildcard