Start

Troubleshooting

Recognizable symptoms, one diagnostic, and one safe recovery action.

Verified 25 September 2026

Check npm prefix -g, then ensure its bin directory is on PATH or open a new terminal.

Run npm ls --depth=0 in the generated app, then rerun npm install and address the first meaningful error.

Use the first meaningful npm error to identify network, permission, or native dependency failure; do not start with broad cache deletion.

Check disk space and the first QVAC error. Return to the base scaffold or use a smaller compatible model before retrying.

Continue device-only. If Node features are needed, check that it is running, reachable, and has approved the requested capabilities.

Public issue reporting will be linked here after the repository and support route are anonymously accessible.