pac-resolver
9.0.2 · 16 Nov 2026MIT34.6M / weekRepositoryHomepagenpmAtom feed
Upgrading pac-resolver From 6.0.2 to 9.0.2
6 releases in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 1
- new
- 3
- fixes
Before you upgrade
Tick each one off as you go- Breaking9.0.0
- Breaking8.0.0
- Breaking7.0.0
Security
- 7.0.1
Fix GHSA-78xj-cgh5-2h22 vulnerability
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
5 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.