We gave someone the Meronq Desktop 0.1.6 installer for their own repo. Connect never ran. The error told them to run pnpm --filter @meronq/desktop fetch:node — a command that only exists inside the Meronq monorepo.
Tauri externalBin already copies meronq-node next to the exe. The Rust host never looked there. It used CARGO_MANIFEST_DIR, which is baked in at compile time. On the build PC the binaries folder still exists, so dogfood lied. On %LOCALAPPDATA%\Meronq Desktop\ it does not. The watchdog retried the miss five times.
0.1.7 searches the exe dir and resource dir first. React chrome (sidebar, Assistants, map island) is in the tag; the reason to cut today is Connect on a machine that is not the build machine.
Canonical write-up: https://meronq.pages.dev/blog/2026-09-10-desktop-0-1-7-installer-sidecar/
Windows installer: https://pub-f4e9aaa767d24ebab1fd7eda766d6a7c.r2.dev/desktop/stable/latest/windows-x86_64-setup.exe
Top comments (0)