Unable to select an element from the Canva on MacOS

[jonathanlemineur-tech]

Since the August 23 update, I am unable to select any element directly on the canvas. Clicking behaves as if the project is in Preview mode.

However, I can still select an element from the Navigator, but it does not highlight on the canvas.

[LilianBarbe]

Same symptom here on 0.1.16 (macOS, Apple Silicon, Astro 7.1.4, Node 24). I dug into it — the canvas is not the problem, the app is silently falling back to a bare dev server on every launch.

Root cause: electron/htmlText.js is missing from asarUnpack.

writeMarkerConfig() writes node_modules/.avb/astro.config.mjs, which does:

const { parsePage, serializePageMarked, resolveChunks, markChunkHtml } =
  require(".../app.asar.unpacked/electron/astroParser.js");

and astroParser.js in turn does require('./htmlText').

In the shipped bundle, electron/astroParser.js is marked unpacked: true in the asar header, but electron/htmlText.js is not — it is still packed inside app.asar. Astro runs in a plain Node child process with no asar support, so the relative require cannot resolve:

$ node -e "import('./node_modules/.avb/astro.config.mjs')"
ERR Cannot find module './htmlText'
Require stack:
- /Applications/Stacki.app/Contents/Resources/app.asar.unpacked/electron/astroParser.js
- <project>/node_modules/.avb/astro.config.mjs

asar header entries:

astroParser.js  -> { size: 123837, unpacked: true, ... }
htmlText.js     -> { size: 3478, offset: '2843150', ... }   # packed

parsesAsModule() does not catch this — the file is syntactically valid and only fails at runtime, when Astro imports it. So the marker config is handed to astro dev --config, Astro fails to start, and the retry falls through to bare: true. The spawned process carries no --config, which is the tell:

node .../node_modules/astro/bin/astro.mjs dev --port 4321 --host 127.0.0.1 --force

That accounts for all three symptoms at once: no outlines / no click selection (no marker injection), full reloads instead of live patching, and the Astro dev toolbar showing up (the devToolbar: { enabled: false } lives in the config that was dropped).

Fix: add electron/htmlText.js to asarUnpack alongside electron/astroParser.js — unpacking electron/** would be more robust against this recurring the next time a sibling module is added. htmlText.js has no requires of its own, so it is the only missing piece.

Workaround, for anyone blocked right now (verified — extract electron/htmlText.js from app.asar into Contents/Resources/app.asar.unpacked/electron/, restart Stacki). The extracted file's SHA-256 matches the integrity hash in the asar header, astroParser.js then loads with its 16 exports, and the generated preview config imports cleanly with devToolbar, compressHTML and the avb integrations present. Undo with a single rm; an app update will overwrite it either way.

Minor suggestion: consider having parsesAsModule() actually import the generated config rather than only checking that it parses. The current check passes on a config that cannot load, so the fallback happens after Astro has already failed and nothing points at the real cause.

[petersimmalugnt]

Same for me

[domidex01]

I open a pr with the fix this issues #16 .
@flowtricks please review and approve the pr.