| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| latest-linux.yml | 2026-04-24 | 538 Bytes | |
| Pixcode-1.33.1-amd64.deb | 2026-04-24 | 179.1 MB | |
| Pixcode-1.33.1-x86_64.AppImage | 2026-04-24 | 235.2 MB | |
| latest.yml | 2026-04-24 | 346 Bytes | |
| Pixcode-Setup-1.33.1.exe | 2026-04-24 | 172.1 MB | |
| Pixcode-1.33.1-arm64.dmg | 2026-04-24 | 202.5 MB | |
| Pixcode-1.33.1-x64.dmg | 2026-04-24 | 207.1 MB | |
| README.md | 2026-04-24 | 2.3 kB | |
| v1.33.1 -- JSON auth store + fix Windows bcryptjs crash from 1.32.0 source code.tar.gz | 2026-04-24 | 2.5 MB | |
| v1.33.1 -- JSON auth store + fix Windows bcryptjs crash from 1.32.0 source code.zip | 2026-04-24 | 2.8 MB | |
| Totals: 10 Items | 1.0 GB | 0 | |
Two changes in one release, bundled as v1.33.1 because 1.33.0 went out without the Windows desktop fix.
Auth DB is now a plain JSON file
The auth store moved off SQLite to a simple JSON file at ~/.pixcode/auth.json. This is a much better fit for a kilobyte-scale dataset (users + tokens + telegram links + a few other bits) than a full database engine. What changes for you:
• Your existing auth.db is converted automatically on first boot — no action needed. The old file is preserved as auth.db.migrated-<timestamp> so you can roll back by hand if anything went wrong. • Your saved credentials, GitHub tokens, and Telegram links all carry over. • No more WAL/SHM files in your .pixcode folder. • No more SQLite locking issues on Windows when two Pixcode processes overlap briefly (after an update). • Easier to back up / inspect / hand-edit — it's just JSON.
Fixed: Windows desktop "Cannot find package 'bcryptjs'" on startup after updating to 1.32.0
v1.32.0 swapped bcrypt for bcryptjs. The in-app update flow (tarball swap into the desktop wrapper's runtime dir) replaced the new code correctly but left node_modules alone — because npm tarballs intentionally don't carry node_modules. Result: the new code looked for bcryptjs and found nothing, the server crashed at boot, and the Electron wrapper showed "Couldn't start Pixcode".
1.33.1 fixes the update flow: after extracting the new tarball, it now compares the new package.json dependencies against the previous one. If they differ, it runs npm install --production in the runtime dir to reconcile node_modules. You'll see the npm output stream into the update modal just like the earlier steps.
If you're stuck on a broken 1.32.0 right now:
• Windows: quit Pixcode, open PowerShell, run: cd "$env:APPDATA\pixcode-desktop\pixcode-runtime" npm install bcryptjs --production --no-audit --no-fund Then relaunch. OR: redownload the 1.32.0 installer from this release — CI is rebuilding it right now with the correct node_modules.
• macOS / Linux desktop: same, cd into the corresponding runtime dir (~/.config/pixcode-desktop/pixcode-runtime on Linux), run npm install bcryptjs.
• Headless (npm install -g): unaffected — your system npm keeps the dep tree aligned.