[Bug] npx impeccable install silently installs nothing on Node v24.16.0 / v26.1.0+

[kenryu42]

What happened?

npx impeccable install prints Downloading impeccable skills..., exits 0, and installs nothing — no .claude/, .cursor/, .agents/ folders are written. No error, no signal that it failed. The CLI's zip extractor stalls mid-extraction on affected Node versions; its promise never settles and the process exits 0.

Steps to reproduce

1. Use an affected Node version: node --version → v24.16.0 or v26.1.0+
2. mkdir /tmp/t && cd /tmp/t && git init
3. npx impeccable install -y

Expected behavior

Skills install into the detected harness folders, with a non-zero exit (or error) on failure. The same command installs all 1,194 files correctly on v24.15.0 and v26.0.0.

Provider & environment

• Provider (Cursor / Claude Code / Gemini CLI / Codex / Copilot / Kiro / OpenCode): N/A — extraction fails before any provider folder is written; affects every harness
• Provider version: N/A
• OS: macOS (Apple M3 Pro) — Node core regression, not OS-bound
• Node.js: v24.16.0

Additional context

Root cause: a Node.js streams regression (nodejs/node#62557 — pause()/resume() became no-ops on destroyed streams; tracked at nodejs/node#63487) breaks the CLI's extract-zip@2.0.1 → yauzl@2.x → fd-slicer read stack. Cypress, Playwright, and Electron hit the identical silent-exit-0 symptom.

Same machine, same bundle (1,194 files), only Node changes:

Node.js	Result	Files extracted
v24.15.0	✅ works	1,194
v24.16.0	❌ silent exit 0	31
v26.0.0	✅ works	1,194
v26.1.0+	❌ silent exit 0	31

Suggested fix: replace extract-zip with node-stream-zip (reads with fs directly, pure JS, zero deps — the same move Cypress/Playwright/Electron made).

Verified end-to-end on v24.16.0: all 1,194 files extract cleanly.

[abdullah1308]

I'm facing the same issue.

[pbakaus]

Thanks for the report! The root-cause pointer to nodejs/node#63487 made this fast to confirm.

Fix is up in #253. One nuance on the suggested approach: I went with fflate rather than node-stream-zip. Both are pure JS (which matters, we deliberately moved off shelling out to unzip in #198 because Windows has no unzip on PATH), and both sidestep the regression. The difference is maintenance: node-stream-zip's last release was ~5 years ago, whereas fflate is actively maintained (released ~1 month ago, 47M weekly downloads, zero deps). It decompresses from an in-memory buffer and never touches the fs stream path, so it's immune on every Node version.

[kenryu42]

Thanks for the fix, fflate is definitely the better choice here. Awesome skill, by the way!