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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@whitetrefoil/pac-generator-server

v0.1.4

Published

A tiny koa server that generates PAC file from config file.

Readme

@whitetrefoil/pac-generator-server

A tiny koa server that generates PAC file from config file.

Usage

Install, Configure, Start

# Install globally
npm i -g @whitetrefoil/pac-generator-server

# Assume here "my_rules.toml" is not existed yet
pac-generator-server my_rules.toml

# Write rules in it
vim my_rules.toml

# Assume the content of "my_rules.toml" is:
#     host = "my.server"
#     port = 48332
#     pacDir = "tests/pac"
#     prefix = "/pac"

# Make dir to put PAC definition files
mkdir -p tests/pac

# Write some definition files
vim tests/pac/test.toml

# Assume the content of "tests/pac/test.toml" is:
#     rules = [
#     "*domain*",
#     "*.subdomain.com",
#     "another.com",
#     ]

# Execute on a existing file will start the server
pac-generator-server my_rules.toml

PAC definition file

The definition file is a TOML file, looks like below:

rules = [
"domain.com",
"*.subdomain.com",
"*keyword*",
]

There are 3 type of rule can be use:

  1. Domain - A rule contains no * will become dnsDomainIs(host,"${rule}")
  2. Sub-domain only - Contains exact 1 * will become shExpMatch(host,"${rule}")
  3. Keyword - Contains 2 or more * will become shExpMatch(url,"${rule}")

Request the PAC from API

curl "http://my.server:48332/my.pac?t=HTTPS&h=localhost&p=12345"

In the above query:

  • t for TYPE, e.g. HTTPS, SOCKS, default is PROXY
  • h for HOST, default is localhost
  • p for PORT, this one is REQUIRED

Changelog

v0.1.4

  • Better docs & keywords.
  • Ignore "lib-esm".

v0.1.3

  • Fix wrong changelog order.

v0.1.2

  • Fix missing bin file in "bin" dir.

v0.1.1

  • Add missing npm publish checklist js.

v0.1.0

  • Initial release.