</>PackageGraphPackageGraph

pac-resolver

npmv9.0.1

Generates an asynchronous resolver function from a PAC file

Adopt with care

pac-resolver is usable, with caveats.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • BMaintenance: grade B, Good.

    Last published 157 days ago. 3 releases in the last 2 years.

  • BWeight: grade B, Good.

    Pulls in 8 transitive packages, about 787 KB installed (at least — some of the tree is still being crawled).

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding pac-resolver to a project.

2
Direct dependencies

Runtime packages this one declares itself.

8
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

787 KB
Install size

Unpacked size of this package plus its entire runtime tree.

3
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

BSD-2-ClauseBSD-3-ClauseMIT

Every license you inherit by installing pac-resolver, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >= 20
Module format
ESM only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the pac-resolver README.

jsFull README ↗
function FindProxyForURL(url, host) {
  if (isInNet(myIpAddress(), "10.1.10.0", "255.255.255.0")) {
    return "PROXY 1.2.3.4:8080";
  } else {
    return "DIRECT";
  }
}

pac-resolver vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
pac-resolverthis page01MIT5 months ago
pkg-dirdeprecated01MIT1 day ago
pac-proxy-agent01MIT1 day ago
find-up04MIT1 day ago
find-up-simple02MIT1 day ago
https-proxy-agent225.1M10MIT1 day ago

Dependencies

Declared by pac-resolver v9.0.1. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (2)

degenerator 7.0.1netmask ^2.0.2

Peer (1)

quickjs-wasi ^2.2.0

Dev (5)

@types/netmask ^1.0.30@types/node ^22.13.0quickjs-wasi ^2.2.0tsconfig 0.0.0typescript ^5.1.6

Used by

Popular packages that depend on pac-resolver.

pac-proxy-agentnpm

A PAC file proxy `http.Agent` implementation for HTTP

↓ 0/wk◈ 1 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of pac-resolver.

netmaskdegeneratorquickjs-wasipac-proxy-agentpac-resolver
pac-resolver dependencies dependents

Frequently installed together

https-proxy-agentnpm

An HTTP(s) proxy `http.Agent` implementation for HTTPS

↓ 225.1M/wk◈ 10 dependents⚖ MIT
@types/nodenpm

TypeScript definitions for node

↓ 0/wk◈ 327 dependents⚖ MITTS
agent-basenpm

Turn a function into an `http.Agent` instance

↓ 0/wk◈ 6 dependents⚖ MIT
http-proxy-agentnpm

An HTTP(s) proxy `http.Agent` implementation for HTTP

↓ 0/wk◈ 5 dependents⚖ MIT
socks-proxy-agentnpm

A SOCKS proxy `http.Agent` implementation for HTTP and HTTPS

↓ 0/wk◈ 3 dependents⚖ MIT
quickjs-wasinpm

Snapshotable JavaScript runtime via WebAssembly. QuickJS-NG compiled to WASM with snapshot/restore support.

↓ 0/wk◈ 3 dependents⚖ MITTS
debugnpm

Lightweight debugging utility for Node.js and the browser

↓ 0/wk◈ 46 dependents⚖ MIT
@types/debugnpm

TypeScript definitions for debug

↓ 0/wk◈ 20 dependents⚖ MITTS

Release history

3 releases in the last two years, typically about 90 days apart.

Recent versions of pac-resolver
VersionPublishedSizeLicense
9.0.1latest5 months ago55 KBMIT
9.0.05 months ago55 KBMIT
8.0.06 months ago55 KBMIT
7.0.12 years ago60 KBMIT
7.0.03 years ago57 KBMIT
6.0.23 years ago57 KBMIT
6.0.13 years ago57 KBMIT
6.0.03 years ago57 KBMIT
5.0.14 years ago52 KBMIT
5.0.05 years ago52 KBMIT
4.2.05 years ago52 KBMIT
4.1.15 years ago52 KBMIT
4.1.06 years ago52 KBMIT
4.0.06 years ago52 KBMIT
3.0.09 years ago—MIT

Overview

pac-resolver is an npm package that generates an asynchronous resolver function from a PAC file. It has 1 known dependents in the graph. The latest version is 9.0.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need generates an asynchronous resolver function from a PAC file and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

tootallnate

Keywords

dnsfilepacproxyresolve

Frequently asked questions

Should I use pac-resolver?

pac-resolver is usable, with caveats.

How do I install pac-resolver?

Run `npm install pac-resolver` to add pac-resolver to your npm project.

How many dependencies does pac-resolver have?

pac-resolver declares 8 direct dependencies and pulls in 8 packages in total once its runtime tree is resolved totalling about 787 KB on disk.

What license is pac-resolver released under?

pac-resolver is distributed under the MIT license. Its dependency tree also includes: BSD-2-Clause, BSD-3-Clause, MIT.

How popular is pac-resolver?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on pac-resolver.

Is pac-resolver still maintained?

The most recent release of pac-resolver (v9.0.1) was published 5 months ago.

Does pac-resolver run install scripts?

No. pac-resolver does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.