You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the clean repro, @replicant026. Found it.
npm/install.js calls unzip to extract the release zip, and Windows doesn't ship unzip. So the download works, extraction fails silently, and stacklit.exe never lands in npm/bin/. On first run you hit "binary not found" because that's all the wrapper knows to say.
Fix in #35 switches Windows to PowerShell's Expand-Archive and makes the install fail loudly if the binary is missing afterward, so this stays visible next time.
I'll ping you here once it's in a release so you can verify.
Activity
thegdsks commentedon May 6, 2026
Thanks for the clean repro, @replicant026. Found it.
npm/install.jscallsunzipto extract the release zip, and Windows doesn't shipunzip. So the download works, extraction fails silently, andstacklit.exenever lands innpm/bin/. On first run you hit "binary not found" because that's all the wrapper knows to say.Fix in #35 switches Windows to PowerShell's
Expand-Archiveand makes the install fail loudly if the binary is missing afterward, so this stays visible next time.I'll ping you here once it's in a release so you can verify.
fix: Windows install + config docs (closes #32, #34) (#35)