pac-resolver
9.0.2 · 16 Nov 2026MIT34.6M / weekRepositoryHomepagenpmAtom feed
Upgrading pac-resolver From 1.0.0 to 9.0.2
26 releases in betweennotes for 13
Reading releases, release notes and advisories…
Counted from 13 of 26 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking9.0.0
- Breaking8.0.0
- Breaking7.0.0
- Breaking6.0.0
- Breaking5.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
Security
Fixes 1 advisory affecting 1.0.0
- Code Injection in pac-resolverhigh · GHSA-9j49-mfvp-vmhm
- 7.0.1
Fix GHSA-78xj-cgh5-2h22 vulnerability
- 3.0.0
This release fixes the MitM vulnerability reported via HackerOne.
Release by release
- Fixed
Update
quickjs-wasito v3.0.0. WASM bytes are now explicitly loaded viareadFile()instead of relying on implicit filesystem I/O.
- Fixed
- Fixed
Update QuickJS integration for
quickjs-wasiv2.2.0. This removes deprecatedunwrapResult()/dispose(false)usage and avoids duplicate sandbox host callback registration when recompiling PAC resolvers.
- Fixed
- Breaking
Set minimum Node.js version to 20
- Fixed
Simplify package.json exports to remove unnecessary imports restriction
- Breaking
- Breaking
Convert to ESM. All packages now use
"type": "module"and compile to ESM output instead of CommonJS. - New
Replace
@tootallnate/quickjs-emscriptenwithquickjs-wasifor running sandboxed PAC file code.quickjs-wasiis a lighter-weight QuickJS WASM runtime built on quickjs-ng with WASI reactor mode. Thecompile()function now takes aQuickJSinstance directly instead ofQuickJSWASMModule, andcreatePacResolver()/pac-proxy-agentare updated accordingly.
- Breaking
- Security
Fix GHSA-78xj-cgh5-2h22 vulnerability
- Security
- Breaking
Use
quickjs-emscripteninstead ofvm2to execute PAC file code
- Breaking
6.0.1 – 6.0.22 releases, nothing new or fixed in the notes
- Breaking
Major version bump for all packages
- Fixed
Convert mocha tests to jest for all packages
- Breaking
11 internal lines (docs, tests, tooling) left out.
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.