docs: how to build the desktop app, and the packaged macOS launch
This commit is contained in:
@@ -148,6 +148,10 @@ npm run dev:server # sidecar on http://localhost:3333, serves the UI from
|
||||
- Workspace packages export their TypeScript source under the `source` condition, which
|
||||
tsx, Vitest, Vite and the sidecar bundle resolve (P2.1). No `build:packages` is needed
|
||||
before running or testing; it builds the `dist/` entries for publishing.
|
||||
- The desktop app (`app/`) has its own dependencies outside the npm workspaces: run
|
||||
`npm ci` in `app/` once, then `npm run tauri:build:mac:arm64` (or the script for your
|
||||
platform). It needs a current Rust toolchain. Set `CI=true` when the build runs without
|
||||
access to Finder, or the DMG step fails while styling the disk image window.
|
||||
- The sidecar registers routes for the files in `dist/` when it starts (`@fastify/static`
|
||||
with `wildcard: false`), so assets from a later build return 404. Restart the sidecar after
|
||||
`npm run build`.
|
||||
|
||||
@@ -99,8 +99,11 @@ data directory as in week 1. Two e2e journeys, B1.6 (first memory search under 5
|
||||
(oversized search query), failed once each when only their spec files ran; both passed in
|
||||
the full runs.
|
||||
|
||||
The Tauri desktop shell was not compiled: the machine's Rust toolchain (1.72) is older than
|
||||
Tauri 2 and the version-4 `Cargo.lock` need.
|
||||
After updating Rust to 1.99.1, the Tauri shell builds for macOS arm64 (`Waggle.app` and
|
||||
`Waggle_0.2.0_aarch64.dmg`, unsigned), and its 30 Rust tests pass. The first packaged launch
|
||||
stayed on "Starting Waggle…" because the shell looked for the sidecar next to the executable
|
||||
(UF-004); with that fixed, the app starts its bundled sidecar on a temporary data directory
|
||||
and opens the onboarding screen.
|
||||
|
||||
## Not run yet
|
||||
|
||||
|
||||
Reference in New Issue
Block a user