Repository navigation
Require VS Code 1.101 for Puppeteer runtime compatibility - #13
Conversation
|
Final local verification artifact: SHA-256: After packaging the updated README/changelog, all 100 archived runtime/webview files were byte-for-byte identical to the installed VSIX payload exercised through the real HTML/PDF export commands in VS Code 1.101.0 / Electron 35.5.1 / Node 22.15.1 on macOS ARM64. Final archive verification passed. Disposable editor downloads, profiles, runtime probe, export fixtures, and PDF inspection script were removed; the verified VSIX is retained locally. No version bump or publication. |
|
Cross-platform CI passed on Windows, macOS, and Linux: https://github.com/atomicdotdev/sherpa-vscode/actions/runs/43965877543 . Local verification also passed: 224 tests, typecheck, universal VSIX/extracted-consumer checks, and production audit (0 vulnerabilities). Actual VS Code 1.101.0 HTML/PDF export commands were exercised on macOS ARM64; Windows/Linux minimum-version Electron-host validation remains unverified. No version bump or publication. |
Problem
Sherpa advertised VS Code 1.97+, whose extension host uses Node 20, while Puppeteer 25 requires Node >=22.12.0. Downgrading to the newest Puppeteer 24 reintroduced nine high-severity production audit findings, including extract-zip vulnerabilities with no patched release. The approved resolution is to raise the editor minimum rather than weaken the audit or maintain dependency backports.
Changes
Why 1.101.0
Verification
npm run typechecknpm test: 224 passed, 0 failed.npm run package:vsixand finalnode scripts/package-universal.mjs: universal archive and extracted nodeatomic consumer verification passed.npm audit --omit=dev --audit-level=low: 0 vulnerabilities.