v1.6.3
Release v1.6.3
Section titled “Release v1.6.3”Desktop startup
Section titled “Desktop startup”-
Fix the
spawn tsx ENOENTstartup error that broke the 1.5.X → 1.6.2 upgrade path (and any first-run/auto-heal seed) when Strata is launched from/Applications:- macOS strips
PATHto/usr/bin:/bin:/usr/sbin:/sbinfor GUI apps launched by LaunchServices. - The app ran the seed through
prisma db seed, which re-spawns the configured commandtsx prisma/seed.ts(frombackend/prisma.config.ts) via PATH lookup — sotsxinbackend/node_modules/.binwas unreachable and seeding died withspawn tsx ENOENT. - Because seeding is a blocking startup step, the failure also produced the misleading “desktop backend on :3456 did not start” post-install check error in
npm run tauri:install.
- macOS strips
-
The seed is now invoked with fully absolute paths — the resolved Node binary (
find_node) plusbackend/node_modules/tsx/dist/cli.mjs(resolved fromtsx’spackage.jsonbinentry) runningbackend/prisma/seed.ts— so no PATH lookup happens anywhere in the startup chain, mirroring the hardening already applied toprisma migrate deploy. -
Developer workflow unchanged:
STRATA_SEED_PROFILE=development npx prisma db seedin a terminal still works as documented.
Verification
Section titled “Verification”- Reproduced the exact reported failure (
Command failed with ENOENT: tsx prisma/seed.ts / spawn tsx ENOENT) on a scratch database under a strippedPATH, then verified the new invocation seeds 13 asset types with exit 0 under the same strippedPATH. - 3 new Rust regression tests for the tsx CLI resolver (
cargo test: 12 passed, baseline 9). - Local gates green: backend build +
test:cov(351 passed, 97.34%) +test:e2e(77 passed), frontend build + coverage (95.7%), docs build, release tooling tests; CI green onmain.
Upgrading
Section titled “Upgrading”If you hit the popup on an existing install: git pull, then re-run npm run tauri:install. The upgrade seed now runs PATH-independently and the app starts normally.