Packages

pac-resolver

9.0.2 · 16 Nov 2026MIT34.6M / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 9.x9.0.2No known advisoryLatest line
  • 8.x8.0.0No known advisoryTo 9.0.2
  • 7.x7.0.1No known advisoryTo 9.0.2
  • 6.x6.0.2No known advisoryTo 9.0.2
  • 5.x5.0.1No known advisoryTo 9.0.2
  • 4.x and older4.2.05 open advisories, worst high · last release Mar 2021, no longer updatedTo 9.0.2

Latest releases

All 29 releases
  1. 9.x · latest line
  2. 9.0.2

    16 Nov 2026
    • Update quickjs-wasi to v3.0.0. WASM bytes are now explicitly loaded via readFile() instead of relying on implicit filesystem I/O.

  3. 9.0.1

    6 Apr 2026
    • Update QuickJS integration for quickjs-wasi v2.2.0. This removes deprecated unwrapResult() / dispose(false) usage and avoids duplicate sandbox host callback registration when recompiling PAC resolvers.

  4. 9.0.0

    1 Apr 2026
    • Breaking

      Set minimum Node.js version to 20

    • Simplify package.json exports to remove unnecessary imports restriction

Dependency tracking

Know when your own dependencies move

pac-resolver shipped 2 new majors in the last 12 months, among 4 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.

  • Advisories reach you

    An email when a critical or high advisory affects a project, before the next install.

  • Upgrades checked first

    Peer ranges, Node, ESM-only and types changes read before you bump.

  • Only what matters

    Majors and breaking notes stay; patches and sibling bumps fold into one line.

How dependency tracking works

Reading releases, release notes and advisories…

Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.