Skip to content
Strata v1.6.3

v1.6.3

  • Fix the spawn tsx ENOENT startup 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 PATH to /usr/bin:/bin:/usr/sbin:/sbin for GUI apps launched by LaunchServices.
    • The app ran the seed through prisma db seed, which re-spawns the configured command tsx prisma/seed.ts (from backend/prisma.config.ts) via PATH lookup — so tsx in backend/node_modules/.bin was unreachable and seeding died with spawn 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.
  • The seed is now invoked with fully absolute paths — the resolved Node binary (find_node) plus backend/node_modules/tsx/dist/cli.mjs (resolved from tsx’s package.json bin entry) running backend/prisma/seed.ts — so no PATH lookup happens anywhere in the startup chain, mirroring the hardening already applied to prisma migrate deploy.

  • Developer workflow unchanged: STRATA_SEED_PROFILE=development npx prisma db seed in a terminal still works as documented.

  • Reproduced the exact reported failure (Command failed with ENOENT: tsx prisma/seed.ts / spawn tsx ENOENT) on a scratch database under a stripped PATH, then verified the new invocation seeds 13 asset types with exit 0 under the same stripped PATH.
  • 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 on main.

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.