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 🙏

© 2025 – Pkg Stats / Ryan Hefner

pac-proxy-server

v1.0.2

Published

a proxy server using pac file to get the proxy strategy

Downloads

4

Readme

pac-proxy-server

Installation

npm i -g pac-proxy-server

usage

During my work, I need to visit some websites via socks proxy, some internal network via my company's http proxy, and others direct. Through all the above can be done via pac, but I still need pac strategy in command line, some paricular application, etc, which do not support pac directly.

My own pac file's FindProxyForURL is something like below:

function FindProxyForURL(url, host) {
  if (defaultMatcher.matchesAny(url, host) instanceof BlockingFilter) {
    return proxy;
  }
+ if (host.match(/^(128\.160|11\.)/) && !host.match(/128.160.180.97/)) {
+    return 'PROXY 128.160.180.97:808'
+  }
  return direct;
}

before use

  • You should have the proxy.pac file, and the proxy address in it is usable

how to use

By passing the proxy.pac file location, this module will use the FindProxyForURL function to figure out which proxy to use, and then send the request through the proxy.

pps --pac ~/.ShadowsocksX-NG/gfwlist.js --port 8088

By default, this module will use socks5 proxy 127.0.0.1:1080 for gfwlist websites. Take a look at ./pac.js.

options

pps --help

Usage: pps [options]

Options:
  --pac <file>   proxy.pac file location (default: "/your/npm/repo/pac-proxy-server/pac.js")
  --port <port>  proxy server's port (default: 8088)
  --timeout <timeout>  each proxy timeout (default: 10000)

unsupported

  • proxy chains