Skip to content

Troubleshooting

Mel edited this page Nov 10, 2026 · 1 revision

Grouped from section 7 of the user guide. Install failures (FUSE, webview, glibc) are under Install.

Node

Symptom Cause What to do
node was not found on PATH node is not installed, or not on the app's PATH install Node.js 22+ from nodejs.org or a version manager, then relaunch
node 22+ is required, found vX node is too old install a newer node, then relaunch
setup screen shows only a node message (no folder named) node fails while the checkout itself is fine fix node, then re-check. The folder is not the problem

Stack checkout

Symptom Cause What to do
no escacs/stack checkout found no saved folder, no ESCACS_STACK, nothing found upward pick stack folder, or export ESCACS_STACK and re-check
… is not a usable stack checkout: tools/stack/cli.mjs is missing the saved or env folder is not the clone pick the folder that contains tools/stack/cli.mjs
a picked folder is refused with … is not a usable stack checkout the app validates a folder before saving it, so a bad pick is never remembered pick the clone instead
… it is not a git checkout with a HEAD commit the folder has no .git with a HEAD clone the stack, or pick the clone

Network and updates

Symptom Cause What to do
component libraries missing from browse the CLI could not sync a remote library and has no cache. It prints a warning: line to stderr, and the app drops stderr on success. Not verified in the app: this row comes from reading the CLI source in the stack checkout: node tools/stack/cli.mjs remote sync <library>
offline network down show and status do not need the network. list syncs remote libraries first and falls back to their cache when the sync fails
check shows an error no network, or the release feed is not reachable (the repo must be public) read the message; retry later. Startup failures show only in the terminal

Import and project

Symptom Cause What to do
nothing listed, (._.) none the stack has no entries of that kind, or the list is empty check the checkout: node tools/stack/cli.mjs list in the stack folder
untracked look-alikes, nothing written: target files exist with different content move them, pick another --to, or delete them. Identical files are fine
not committed in the stack: can't import the entry is only in the stack's working tree commit it in the stack checkout, then retry
cannot resolve path or path is not a directory the project path is gone or is a file pick the folder again
(o_O) not found a route the app does not have use browse or installed in the top bar

See also: Install, Settings and Storage, Updates and Releases.

Clone this wiki locally